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.
Build: NetBeans IDE 8.0 (Build 201403101706) VM: Java HotSpot(TM) 64-Bit Server VM, 24.51-b03, Java(TM) SE Runtime Environment, 1.7.0_51-b13 OS: Windows 7 User Comments: jherkel: I compiled source files from command line via maven clean install Stacktrace: org.netbeans.modules.deadlock.detector.Detector$DeadlockDetectedException: Editor Parsing Loop (201403101706) at org.netbeans.api.java.classpath.ClassPath$Entry.getRoot(ClassPath.java:776) at org.netbeans.api.java.classpath.ClassPath.createRoots(ClassPath.java:284) at org.netbeans.api.java.classpath.ClassPath.getRoots(ClassPath.java:268) at org.netbeans.api.java.classpath.ClassPath.findResource(ClassPath.java:448) at org.netbeans.modules.web.beans.navigation.actions.WebBeansActionHelper.hasResource(WebBeansActionHelper.java:272) at org.netbeans.modules.web.beans.navigation.actions.WebBeansActionHelper.hasJsr330(WebBeansActionHelper.java:209)
Created attachment 146292 [details] stacktrace
I didn't get any stack trace, but I used VisualVM to sample the CPU usage and I saw that Editor Parsing Loop (201403101706) is blocking 1 CPU core forever, so I think it's relevant to this bug report. Problem: when I have some specific files opened in NetBeans in split mode (left right - see screenshot), NetBeans blocks 1 core of my CPU for ever. The only solution is to close the opened files. It also happened without split mode. The attached zip file is a NetBeans Maven web app project that contains a sample of the real project in which I encountered this bug. Steps to reproduce: 1. Start NetBeans on Windows 8 x64 Jdk 8 u05 x32. I have the latest NetBeans with the latest updates. 2. Import the project 3. Open those 3 xhtml documents as shown in the screenshot. 4. Click through them a few times to activate the editor. I mean to click somewhere in the shown code in all 3 of the files, one by one. 5. You should see that NetBeans is blocking one core now with the Editor Parsing Loop (201403101706) if you activate the sampler in VisualVM !!! All attached files starting with zmirc* are related to this comment. I hope this will reproduce the error because it's extremely annoying because it heats up my laptop and it kills the battery very fast due to the useless 100% cpu usage.
Created attachment 148953 [details] All screenshots mentioned + the sample NetBeans project to reproduce the bug
Additional information for reproducing: - You should also download the dependencies specified in the pom.xml project through NetBeans, so that you will not have errors in the editor view. (In reply to zmirc from comment #2) > I didn't get any stack trace, but I used VisualVM to sample the CPU usage > and I saw that Editor Parsing Loop (201403101706) is blocking 1 CPU core > forever, so I think it's relevant to this bug report. > > Problem: when I have some specific files opened in NetBeans in split mode > (left right - see screenshot), NetBeans blocks 1 core of my CPU for ever. > The only solution is to close the opened files. It also happened without > split mode. > > The attached zip file is a NetBeans Maven web app project that contains a > sample of the real project in which I encountered this bug. > > Steps to reproduce: > 1. Start NetBeans on Windows 8 x64 Jdk 8 u05 x32. I have the latest NetBeans > with the latest updates. > 2. Import the project > 3. Open those 3 xhtml documents as shown in the screenshot. > 4. Click through them a few times to activate the editor. I mean to click > somewhere in the shown code in all 3 of the files, one by one. > 5. You should see that NetBeans is blocking one core now with the Editor > Parsing Loop (201403101706) if you activate the sampler in VisualVM > > !!! All attached files starting with zmirc* are related to this comment. > > I hope this will reproduce the error because it's extremely annoying because > it heats up my laptop and it kills the battery very fast due to the useless > 100% cpu usage.
To make your life eaasier... Locations of the 3 xhtml files that have to be opened in order to reproduce the bug: src\main\webapp\resources\pages\medic\profile.xhtml src\main\webapp\resources\pages\home.xhtml src\main\webapp\WEB-INF\templates\master.xhtml Open them and put them in split view (left-right), as in the attached screenshot. (In reply to zmirc from comment #4) > Additional information for reproducing: > - You should also download the dependencies specified in the pom.xml project > through NetBeans, so that you will not have errors in the editor view. > > > (In reply to zmirc from comment #2) > > I didn't get any stack trace, but I used VisualVM to sample the CPU usage > > and I saw that Editor Parsing Loop (201403101706) is blocking 1 CPU core > > forever, so I think it's relevant to this bug report. > > > > Problem: when I have some specific files opened in NetBeans in split mode > > (left right - see screenshot), NetBeans blocks 1 core of my CPU for ever. > > The only solution is to close the opened files. It also happened without > > split mode. > > > > The attached zip file is a NetBeans Maven web app project that contains a > > sample of the real project in which I encountered this bug. > > > > Steps to reproduce: > > 1. Start NetBeans on Windows 8 x64 Jdk 8 u05 x32. I have the latest NetBeans > > with the latest updates. > > 2. Import the project > > 3. Open those 3 xhtml documents as shown in the screenshot. > > 4. Click through them a few times to activate the editor. I mean to click > > somewhere in the shown code in all 3 of the files, one by one. > > 5. You should see that NetBeans is blocking one core now with the Editor > > Parsing Loop (201403101706) if you activate the sampler in VisualVM > > > > !!! All attached files starting with zmirc* are related to this comment. > > > > I hope this will reproduce the error because it's extremely annoying because > > it heats up my laptop and it kills the battery very fast due to the useless > > 100% cpu usage.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss