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 # : 200808170243 ] [ JDK VERSION : 1.6.0_07 ] Product Version: NetBeans IDE Dev (Build 200808170243) Java: 1.6.0_07; Java HotSpot(TM) 64-Bit Server VM 10.0-b23 System: Linux version 2.6.26-1.slh.3-sidux-amd64 running on amd64; UTF-8; en_US (nb) Userdir: /home/sasbeb/.netbeans/dev Editing is very painful... Updates/keybing responsiveness is really bad. Attaching a thread dump
Created attachment 67841 [details] StackTrace of issue
It looks like the memory usage is very high, could that be the problem? PSYoungGen total 127936K, used 85014K [0x00007f97bd4b0000, 0x00007f97c7f50000, 0x00007f97c7f50000) eden space 101888K, 83% used [0x00007f97bd4b0000,0x00007f97c27b5b58,0x00007f97c3830000) from space 26048K, 0% used [0x00007f97c3830000,0x00007f97c3830000,0x00007f97c51a0000) to space 36544K, 0% used [0x00007f97c5ba0000,0x00007f97c5ba0000,0x00007f97c7f50000) PSOldGen total 349568K, used 349567K [0x00007f97a7f50000, 0x00007f97bd4b0000, 0x00007f97bd4b0000) object space 349568K, 99% used [0x00007f97a7f50000,0x00007f97bd4afff0,0x00007f97bd4b0000) I also noticed on my build (I am on Mac OS X) that the memory meter climbs very steeply, and the size of the process in Activity Monitor is very big. Looks like there is a giant memory leak. Given the number of complaints about this issue, I think this deserves a higher priority than P3 -> changing to P2.
Also... Can you guys look at making a netbeans.conf at install time? I don't think a "one size fits all" is appropriate until the jvm can self-configure at runtime. The installer knows which jvm, memory, etc so it could set appropriate values for the "out of the box" experience.
Most likely caused by the very big memory usage, similarly to issue #144755 and issue #143234. I do not see any really specific to the editor here, so passing to the performance team. Adding core team to cc to answer the netbeans.conf question.
The reporter also filed issue 143234 which has the same symptoms. Also experienced OutOfMemoryError - issue 144298. On the mailing list he also said "Looks like I can run for about 2 hrs before I get really sluggish." Issue 144755 is again very similar. All indicates a memory leak. So what we need firts is a heap dump/histogram to see what takes up the whole memory. Sasbeb, can you create it and make it available for us (as described in issue 143234)? It would help a lot to diagnose the memory leak. Thanks. We can use issue 143234 for tracking this problem. *** This issue has been marked as a duplicate of 143234 ***
As for netbeans.conf, there is no max heap specified explicitly, it is computed by the launcher based on the actual physical memory of the system. You can find this in the netbeans.conf: # Note that a default -Xmx is selected for you automatically. # You can find this value in var/log/messages.log file in your userdir. # The automatically selected value can be overridden by specifying -J-Xmx here # or on the command line. This algorithm boils down to following figures on common memory sizes: Xmx CMS 512M 96M No 1G 160M No 2G 360M Yes
Removing [65cat] from issue summary since this issue is duplicate of Issue 143234 submitted for [65cat]