Created attachment 82151 [details]
messages.log

Created attachment 82152 [details]
dump file

@vstejskal: I'm not sure, but it looks like problem during scanning. Maybe we are not able to utilize memory usage more
and it just happens.

@reporter: Please increase maximal available memory -Xmx to higher. It can help.

Do you have a heapdump? If not could you please change your IDE so that it generates one when OOME happens next time and
then upload the heap dump to editor.netbeans.org? http://wiki.netbeans.org/FaqMemoryDump
Thanks

I have a heapdump file, how do I upload it to editor.netbeans.org?

I upped Xmx to 1024M and that solve the problem with one project, however during project scanning the memory goes as
high as 800M.  That is with a single set of projects open, and I used to work with up to 4 sets of projects at once in 6.5.

Eventually even at Xmx1024 it ran out of memory.

"how do I upload it to editor.netbeans.org?" - Go to http://editor.netbeans.org, in the right hand side menu click
'Files' and then 'Add new file'. This will let you upload the heapdump. Please give it some meaningful name. Thanks

The heapdump is 464M, bigger than the file limit at editor.netbeans.org.  Is there a way to reduce the size?

Can you somehow split it to two/more parts and upload them separately? I think for example 7zip allows creating archives
of specific size and it's available on both Win and Linux (among others). Thanks

I assumed that it wouldn't compress well, as it turns out zipping it reduced it to < 100M  It's uploaded

Thanks!

There are 282 instances of the javac compiler (as can be seen from the uploaded heapdump). Looks like an incarnation
of #162133, which should be fixed in the current dev build.

*** This issue has been marked as a duplicate of 162133 ***