I just started NB 6.7, opened one of our projects and clicked into a source -> OutOfMemory. It could not even report the
issue from within NB. 512 MB was not enough. Maybe a memory leak. Attaching everything I have of the incident.
Created attachment 84177 [details]
Created attachment 84178 [details]
Created attachment 84179 [details]
Created attachment 84180 [details]
Created attachment 84181 [details]
Created attachment 84182 [details]
I have to raise the priority, because I cannot work with NB 6.7 because of this.
Also, I cannot attach the heap dump (as zip), because it is 161 MB.
This happens on ANY of our sources. Just open 3 small Java sources -> OOM. This is a J2SE project.
I have standard settings and Java tasklist disabled.
This is interesting: If I ENABLE Java tasklist and let it finish its scanning, then I can open sources without OOM.
This is fatal, because disabling the tasklist was recommended by a popular german news service:
Can you please attach the heap dump(s) here:
The heap dump is crucial for resolving OOME - also can you increase your heap size to check whether it helps?
BTW are you using JavaFX modules? Can you tell me which version? The ones that shipped with NB 6.5.1? Thanks for the info.
I am not using the JavaFX modules. This is a fresh install with a fresh user dir.
The machine has 4 GB of memory, so NetBeans already allocates 512 MB. That should be enough to open 3 Java sources. And
it always (before 6.7) was enough. Although I never disabled the tasklist in earlier versions.
Uploaded the heap dump: http://editor.netbeans.org/servlets/ProjectDocumentList?folderID=356
It seems like the memory is filled by javac but assigning to Dusan to investigate and fix. Max, if you are able to fix
it please take it back and go for it but from my chair it seems like Dusan's territory.
Are you able to reproduce the issue in the current dev build (I have fixed a memory leak in the initial scanning two
weeks ago)? Thanks.
Dusan, do you have the issue number of the fixed leak or changeset that fixed it? QA wants to have the fix for this in
http://hg.netbeans.org/main-silver/rev/3575a6304958 has been already ported into patch1 (see issue #166800).
It would be great if tboerkel can verify that it is ok in today's build from
after the today's build is actually published there. Verification in the trunk would be good as well since we could then
close this issue as fixed (if it is fixed in the trunk).
I just tested today's build (6.7.1 RC). The OOM is gone allright-
BUT: It does project scanning on opening of a project, despite the fact that I have turned Java Tasklist OFF.
But the whole idea behind turning the Java Tasklist OFF (as suggested by the german news service) was to get rid of that
Based on the last tboerkel's comment, closing as fixed.
BTW: All NB 6.0 - 6.5 releases perform scanning on opening of a project regardless the Java Tasklist is ON or OFF. Only
rescanning of dependent files on modifications is not performed if the Java Tasklist is OFF. This is changed in NB 6.7.
*** Issue 168503 has been marked as a duplicate of this issue. ***
v in 6.7.1
*** Issue 168419 has been marked as a duplicate of this issue. ***