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.
Summary: | Netbeans runs out of memory | ||
---|---|---|---|
Product: | javaee | Reporter: | _ viendu <viendu> |
Component: | JSP | Assignee: | Marek Fukala <mfukala> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | rkubacki |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ viendu
2005-11-08 21:47:53 UTC
JDK version, OS? If you run on JDK 5 what kind of OOME - Java heap, perm gen, native resources? Marek did some performance fixes in the code folding. According to the stack the code folding is doing something. Marek, can you look at this? Please in the next time, attach the stack as an attachment. I did rewrite the JSP folding before two months due to some performance reasons, but the reason wasn't memory consumption. I doubt that the folding is responsible for the shootin up memory. It is probable that the folding hirarchy asks fold manager to get folds when the files are closing (do not ask me why). I fixed some memory leaks in JSP editor on November 3th so the fixes should be in your build. Reporter, can you please verify that the same problem exists in latest build? Or if you really feel that the problem is in the JSPs, can you please attach the JSP files? Or the whole web project? Just for sure, isn't netbeans taking 100% of the CPU time before the OOM? Petre, please do not blame every problem on the folding once you see it in the thread dump :-) It is possible that the problem is caused by some neverending loop in the JspFoldManager. Since the IDE is responsible even it takes 100% of CPU then after a time the OOME is thrown probably due to fact that the folding allocates new and new objects chained to each other. There was an issue #69342 which could caused this. I will add a loop-checking code just for sure. fixed - a loop detection code added. If a loop is detected a warning message is printed into IDE output with along with the document. User is asked to file a new issue and put the document content into the report. IMHO this is the best way how to fix the syntax support bugs. Checking in JspFoldManager.java; /cvs/web/jspsyntax/src/org/netbeans/modules/web/core/syntax/folding/JspFoldManager.java,v <-- JspFoldManager.java new revision: 1.43; previous revision: 1.42 done Verified in NetBeans 5.0 FCS build #200601251500. We would appreciate if you could confirm that this does not happen anymore. Thanks for your cooperation and report ! I have been runing the 5.0 release for a while now and having seen this problem. If I do see it again, I'll report it. |