This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I have a project that includes two other projects. When I attempt to run or debug a class in the project, the execution of the class is delayed for minutes until I get a dialog that claims that there was a compilation error, which there wasn't. If I tell it to run anyway, it runs the class fine. There is some thread deadlock/starvation or timeout going on that is delaying the execution. I've attached a few stack traces to help diagnose the problem.
Created attachment 69664 [details] Thread dumps during times where NetBeans was paused for minutes waiting for something to happen before running the code
Could you please tell us which compilation error appears in the dialog. Thanks.
Hm, it seems that the initial scan is still running - was that soon after project opening/IDE start? I do not think we can execute the project (using CoS approach) before the initial scan - the class files to be executed may not exist yet. Regarding the warning dialog: it checks not only the one class, but whole project with all dependencies. Weren't there any compilation errors in the whole project+dependencies? No error badges? Thanks.
NetBeans has had all the projects opened for hours. This happens every time I run the class in the project. Also, when I run the project, it tells me that it has to wait for a classpath scan yet again, but that happens fairly quickly and it continues. I'll capture the dialog the next time it pops up.
Created attachment 69671 [details] Dialog that appears minutes after run execution claiming that there are errors when there are none
Reporter provided us with requested information - removing INCOMPLETE keyword.
For the extraordinary long waits, steps to reproduce may be necessary. A log produced by the IDE with: -J-Dorg.netbeans.modules.java.source.usages.RepositoryUpdater.level=0 right before the Run action might suffice. Might be related to issue #147438. As for the "compiled with errors" dialog, please take a look into the ${userdir}/var/cache/index/<highest number>/ - each "s<number>" directory here corresponds to a source root on some classpath, mapping is in the segments file. Under the "s<directory>" there is directory "errors", which contains ".err" and ".warn" files (mapping to compiler errors and warnings). When the dialog appears, there needs to be at least one ".err" file somewhere in the errors directories corresponding to the classpath. It is necessary to analyze whether the errors in the .err file(s) is correct or not (in which case we need to find out why the incorrect error appeared).
Since requested additional information haven't been provided this issue was closed as INVALID. However, we still consider your report important for next development. Therefore, please, if you experience this issue again feel free to reopen it and submit additional information as well. Thank you for your support.