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.
the javaw.exe process uses between 50 and 70% CPU. Sometimes it drops and the IDE behaves perfectly, but then suddenly it goes up again. Product Version = NetBeans IDE 7.0.1 (Build 201107282000) Operating System = Windows 7 version 6.1 running on intel64bit Java; VM; Vendor = 1.6.0_26 / 1.7 Runtime = Java HotSpot(TM) 64-Bit Server VM 20.1-b02
Created attachment 113574 [details] a snapshot while high CPU usage
The same thing happens with 7.1 beta
I see one (perhaps?) suspicious thing: nu.validator.htmlparser.impl.CoalescingTreeBuilder.accumulateCharacters() 38996 ms (13,2%) for 63 invocations Marku, can you have a look, please? Thanks.
Created attachment 114875 [details] profiling file during high cpu usage. Product Version: NetBeans IDE 7.1 (Build 201112071828) Java: 1.6.0_26; Java HotSpot(TM) 64-Bit Server VM 20.1-b02 System: Windows 7 version 6.1 running on amd64; Cp1252; fr_CH (nb) User directory: C:\Users\stef\.n More data to help. I was just editing a file (php) and saving
Created attachment 115051 [details] Profile during High CPU usage. Having a similar problem with HIGH CPU usage making the IDE unusable. I was merely adding some code and formatting the existing code. IDE was so slow it was taking about 20 seconds to delete a single newline character. I should note that the project that I'm working on is quite large. Product Version: NetBeans IDE 7.1 (Build 201112071828) Java: 1.6.0_16; Java HotSpot(TM) Client VM 14.2-b01 System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb)
I had the same problem. Closing the Task-Window solved it. see also: http://netbeans.org/bugzilla/show_bug.cgi?id=205603#c5
On Windows 7 64-bit CPU usage can be reduced by running Netbeans in compatibility mode (XP SP3). Still high memory usage, but CPU is not so much as before. Luck.
>nu.validator.htmlparser.impl.CoalescingTreeBuilder.accumulateCharacters() >38996 ms (13,2%) for 63 invocations This method is called very often during parsing/lexing so if there's no heap memory and GC runs heavily, then it may seem to consume all the time. The main reason is likely the lack of heap memory. I believe it has been already fixed by the changes done to the issue 207991 - Large project hangs Netbeans 7.1 indefinitely. *** This bug has been marked as a duplicate of bug 207991 ***