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.
Java Editor does not highlight compilation error, although file is marked as having errors in the Projects view Product Version = NetBeans IDE 8.0 RC1 (Build 201402242200) Operating System = Windows 7 version 6.1 running on amd64 Java; VM; Vendor = 1.7.0_51 Runtime = Java HotSpot(TM) 64-Bit Server VM 24.51-b03
Created attachment 145943 [details] IDE log
Is anything happening here? It's been a month and this bug is really annoying. It basically renders the whole IDE useless if a Java source file has errors but there is no quick way to identify where the error is.
Please try upgrading to 8.0 fcs, there were addressed such issues in the final release
(In reply to Jiri Prox from comment #3) > Please try upgrading to 8.0 fcs, there were addressed such issues in the > final release I have. Problem still occurs though I cannot precisely tell you how to reproduce it. Seems to happen when editing a lot of files in a big project. If it happens again, I will try and upload the log here.
Isn't background indexing in progress whenever you notice the file errors are not marked in editor? FYI, the task that draw error marks in editor waits for background scan to be finished.
(In reply to Dusan Balek from comment #5) > Isn't background indexing in progress whenever you notice the file errors > are not marked in editor? FYI, the task that draw error marks in editor > waits for background scan to be finished. I'm not sure if some indexing is running. At least I didn't see any progress bar or other indicator that there is a Netbeans process running. Anyway, the status I described did not change for minutes. Actually, I had to restart Netbeans to get Java editor working again. So either the background scan is way to slow or it was not the problem.
Same situation here. Eventually after the yesterday's update.
Same problem here. Very annoying.
Unfortunately, it is hard to do anything without a reproducible test case. Next time you observe the problem, could you please capture a thread dump and profiler snapshot (invoking the 'Profile the IDE' action and waiting for a while) and attach it to the issue? Thanks.