Build: NetBeans IDE 6.8 RC1 (Build 200911252200)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.3-b01-100, Java(TM) SE Runtime Environment, 1.6.0_17-b04-237-10M3013
OS: Mac OS X, 10.6.2, x86_64
GUEST: Project was scanned
GUEST: Starting up Netbeans
GUEST: Still geting this error with default install of latest Daily build. Was not doing anything but waiting for the "projects scan" to complete. I notice that this error possibly relates to the failure to copy a complete set of a php project's app and web files to the local web Document folder as specified in the php properties dialog box.
nehalem: I have tried to open and have the new netbeans scan my work project many times. Each time it runs out of memory.
GUEST: Just sitting there, with 'Scanning Projects' running.
GUEST: this error occoured while "scanning projects" just after starting netbeans.
The project is a php project.
java.lang.OutOfMemoryError: Java heap space
Created attachment 91891 [details]
nahlem, could you please send us the heapdump generated by the IDE? Either attach it here or send it to email@example.com. Thanks
(In reply to comment #2)
> nahlem, could you please send us the heapdump generated by the IDE? Either
> attach it here or send it to firstname.lastname@example.org. Thanks
How do I do this? I should mention this is a PHP project as well. Seems the PHP scanner probably has some issues.
Go to http://netbeans.org/projects/editor/downloads and upload the file there and tell us what file it is. You will have to be logged in. If the file contains data that you don't want to be publicaly visible, I'll move the file to an internal storage here at Sun. Thanks
Actually, what I don't understand is where do I get that heapdump that it generates?
Also, I can confirm the same behaivor on RC2. In addition all of us who have tried it at my workplace are having this issue.
OH, wait, on RC2 I didn't have the problem, but a co-worker did. Strange. I'll keep playing with it.
Here is guide how to generate heapdump:
Ok, I've tried to set my netbeans to automatically create the heap dump when it happens. With RC2 it's happening less, but in visual VM I just did, it came dangerously close.
I can upload that one if you would like (even though it doesn't create the exception).
(In reply to comment #8)
> Ok, I've tried to set my netbeans to automatically create the heap dump when it
> happens. With RC2 it's happening less, but in visual VM I just did, it came
> dangerously close.
> I can upload that one if you would like (even though it doesn't create the
Yes, please. Thanks. It's better than nothing. But if you manage to salvage a dump from the real OOME please upload it as well.
Okay, I'll upload. Please remove quickly as it is sensitive. It's also about four hundred mb.
Finally. I am having a hard time staying with RC2. The IDE is always comsuming 30 to 100% of my cpu. Maybe you could see if something points to that too. This is after all scanning and no tasks are being performed in the bottom right status bar.
I don't see an upload option on that downloads page.
(In reply to comment #11)
> I don't see an upload option on that downloads page.
I'm afraid that you will have to join the project (editor.netbeans.org) as an observer.
Well this is still happening on the release for us. I will give me heap but can't figure out how to join that group. Is there no easier way to send this stuff to you guys.
I think in 6.9dev builds there is, see issue #173477. However, I'm not sure if the same can be done from 6.8. Jindra might know more and/or suggest a workaround for 6.8 users like yourself. Jindra, could you please help? Thanks
Re. joining the editor project - It's a bit unusual, but all you have to do is to click 'Bookmark This Project' from the project's page (eg. editor.netbeans.org). This will add the project to your 'My Page' and also grant you the observer role. Very intuitive, eh? :-)
Issue #173477 is fixed only in trunk, I didn't do it for 6.8 because I'm not sure how long it might take to upload heapdump files and it needs to be well tested before releasing it.
Ok, finally added a heap dump. It's called "Memory exception heap dump " on that page.
I hope it helps. Netbeans 6.8 has really been problematic for us. With the latest updates it's not only constantly giving me a heap overflow, but also constantly running the CPU. Again, this seems pretty common with my team. I've finally reverted to 6.7.1 since it's simply unusable. I'll do anything I can to help, hope this bug isn't buried too low now.
Thanks, I moved the file to http://netbeans.org/projects/editor/downloads/download/Issues%252F177899%252Fheapdump-2-15-2010.hprof.zip
The biggest objects on the heap seem to be from subversion module:
org.netbeans.modules.subversion.DiskMapTurboProvider#1 ... 30,373,838
org.netbeans.modules.subversion.DiskMapTurboProvider$1#1 ... 30,371,376
java.util.concurrent.ConcurrentHashMap#23 ... 30,371,352
java.util.concurrent.ConcurrentHashMap$Segment#23 ... 30,371,256
1) It seems you have too much entries in subversion cache. Could you check if you have your home dir versioned? Is there by any chance .svn folder?
2) Please delete the whole ~/.netbeans/6.8/var/cache/svncache folder and run IDE with -J-Dorg.netbeans.modules.subversion.FileStatusCache.recursiveScan=false - does this help?
3) Start IDE with -J-Dorg.netbeans.modules.subversion.level=500 and attach the message log after few minutes of IDE's work (~/.netbeans/6.8/var/log/message.log)
Ok, follows your instructions:
1) Ok, yes there was a single .svn folder in my home directory. NO IDEA WHY. I deleted it (no subfolder had a .svn folder). I did delete my cache.
2) I ran it with this both of the startup arguments you provided (I think, I added it to the netbeans.conf). I started up netbeans and I got the same memory exception.
3) I attached my message.log in the upload directory. Please take a look.
I looked at the message log and there seems to be no problem with subversion now, no excessive scanning, running svn status commands only inside '/Applications/MAMP/htdocs' which is svn versioned (that's versioned intentionaly, i presume?).
Could you then do the same steps as the last time (delete the svn cache, setting the switches) and upload:
1) generated heap dump
2) created ~/.netbeans/6.8/var/cache/svncache
3) the message log again
There will probably be some new interesting information
BTW, you upload the message.log directly to 'http://netbeans.org/projects/editor/downloads'. Please upload these files to the folder representing the corresponding issue, so we have all the related files together in one folder.
Okay, I had to revert for a while to deal with a deadline. I did download m1 of 6.9 and can confirm that this problem still happens with that. I will get you what you requested very soon.
(In reply to comment #22)
> Okay, I had to revert for a while to deal with a deadline. I did download m1
> of 6.9 and can confirm that this problem still happens with that. I will get
> you what you requested very soon.
We've recently made some performance improvements in subversion support, could you please test and provide requested info with the latest dev build (http://bits.netbeans.org/download/trunk/nightly/latest/)?
(In reply to comment #23)
> We've recently made some performance improvements in subversion support, could
> you please test and provide requested info with the latest dev build
Still happened. Want me to provide info from the dev build or 6.8?
> Still happened. Want me to provide info from the dev build or 6.8?
Hi, I have uploaded the requested dumps (archived). I put in a single file in a folder called "Bug 177889". Please remove after getting in case there is something private contained within. Please let me know if that provides the data needed.
BTW, not sure if it makes a difference but I have a new machine. I guess the out of memory issue (or heap amount available) is not tied to RAM since my new machine has a lot more (8gb).
Hi, thanks for the files, I looked at your heap dump and message log.
The heap dump does not indicate any excessive memory consumption (used memory is about 70MB), subversion does not use as much memory as it was indicated by the first heap dump you provided (probably because you deleted the subversion cache on disk).
I would say the error you're getting is caused by a memory usage peek while your files are being scanned, because the message log contains:
java.lang.OutOfMemoryError: Java heap space
Try to increase allowed memory size (run IDE with -J-Xms1024m -J-Xmx1024m switches, it could help). If you still get the error even with the switches, report it with the exception reporter in IDE.