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.
This bug was originally marked as duplicate of bug 218828, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 7.3 Beta (Build 201210011125) VM: Java HotSpot(TM) 64-Bit Server VM, 20.10-b01-428, Java(TM) SE Runtime Environment, 1.6.0_35-b10-428-11M3811 OS: Mac OS X Maximum slowness yet reported was 10130 ms, average is 10130
Created attachment 125422 [details] nps snapshot
Hi! Actually this is indeed the duplicate of the mentioned bug. The problem is that the fix was not done in time for beta build... So, you can try some recent nightly build. Thanks, =Andrew *** This bug has been marked as a duplicate of bug 218828 ***
Sounds good. Another performance issue, when I debug a project which malloc 500M memory, it is very slow, UI even frozen. BTW., as I back to C development for big data, so I have switched to lightweight IDE now. Anyway, thanks for Netbeans team providing the great IDE for java these years. Thanks, Pprun
(In reply to comment #3) > Another performance issue, when I debug a project which malloc 500M memory, > it is very slow, UI even frozen. How much total memory is there on the machine? Have you got slowness reports from this case in particular?
The latest slow report to: http://statistics.netbeans.org/analytics/exception.do?id=621567 Running as the normal mode, the program does not use memory memory, at most 50M, this issue still present. So please don't focus on my latest comment (500M memory, which was the big-mem mode). The GDB log attached following
Created attachment 126442 [details] the netbeans profiler snapshot the netbeans profiler snapshot
thanks, it looks like terminal is spending too much time in EDT, will address the issue as the bug 220726
Created attachment 126454 [details] cut version gdb log file
The gdb log file is very large 41.8M. I almost find the cause, it seems the gdb eats/prints the input (the content of a tag in the indexing file). And because the body of the tag is very large, so the slowness. The attached cut version, removing most the text (char *), please find or grep the pattern "<many text was removed here>". Therefore, the key point is how to avoid this case, as currently I am using codelite IDE, it works fine.
Hi, I will close this particular issue as duplicate of 218828 as original problem reported here is the duplicate of bz#218828. The problem with gdb is recored as issue http://netbeans.org/bugzilla/show_bug.cgi?id=220726 Please use the bz#220726 to track slowness problem while debugging. Thanks, Maria *** This bug has been marked as a duplicate of bug 218828 ***