Running Anonymous Apex gives Unhandled exception: java.lang.NullPointerException
Windows 10 x64 Webstorm 2019.2 JDK 11
After upgrading to 2.0.7.4, I was unable to run any code in anonymous apex, with the error “Unhandled exception: java.lang.NullPointerException”, and the following in the logs:
2019-08-05 16:30:20,119 [ 651720] WARN - .IlluminatedCloudExceptionUtil - java.lang.NullPointerException at com.illuminatedcloud.intellij.toolwindow.apex.AnonymousApexToolWindow$7.run(SourceFile:510) at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:894) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:169) at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:591) at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:537) at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:59) at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:156) at com.intellij.openapi.progress.impl.CoreProgressManager$4.run(CoreProgressManager.java:408) at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:294) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)
Once I selected a log level this issue did not occur again.
Comments (4)
-
repo owner -
repo owner Issue
#1384was marked as a duplicate of this issue. -
repo owner Issue
#1385was marked as a duplicate of this issue. -
repo owner - changed status to resolved
Delivered in 2.0.7.5.
- Log in to comment
Okay, good to know. I'll take care of it in the next build. Thanks for reporting!