Community
Participate
Working Groups
This error may be a WST or a GEF error, so I may have assigned it wrong: OutOfMemoryError: PermGen space occurs frequently when working with XML files (WSDL). The error may actually not occur when working with an XML file, but can actually occur when doing another task, which means that it isn't that easy to make a precise report about this problem.
Created attachment 39901 [details] Log with stack dumps
Created attachment 39902 [details] Configuration details for current setup
Which editor do you use? Does the OOME happen with a speciif workflow in WSDL? Note: The NPE in AbstractTextEditor.updateCaret(...) is a followup of the errors in the model (SAXParseException).
I'm using the WSDL editor, and it doesn't seem to really depend on the WSDL source, which I generated from Axis Java2WSDL and then edited to tweak it. I have also been getting this error without any stack dump after this report was filed. The only thing I actually can tell is that it seems to be related to editing WSDL or possibly also XSD files. This error didn't occur when I was editing XSD files in M6, but since then the graphical representation has changed and that may be related. Earlier I didn't edit WSDL, so I can't really tell if M6 was better there. I usually work by switching between editing the XML code and the graphical representation. Sometimes it's easier to do pure XML editing and sometimes not.
Now it seems like the editor isn't the culprit after all, but something else. This isnce I got the error during a session where I didn't edit the WSDL. (but there are WSDL files in the workspace) so the error can actually be caused by another item like WSDL validation or something completely different. (hard to tell when the message in the log just states that it's out of PermGen Space and nothing more).
This error still occurs in 3.2RC4 with updated EMF and GEF.
One idea is that this bug may be related to Bug 140879, which I filed as a different bug due to the fact that the symptoms are different.
I have no idea how an out of memory error occurs here but I think more info is required before we can solve this. I think you should also break this bug into separate bugs addressing each of the stack traces. The 'SAXParseException' stack traces illustrates a problem between an Axis creation wizard which modifies web.xml which then tries to load an XML Schema and bombs out. It looks like it's somehow trying to retrieve an HTML file instead of an XML Schema. Please open a separate bug for that against the wst.xml component and we can track it further. Let use this bug to track the mysterious out of memory problem you're hitting. Can you provide more specific steps that lead you from Axis Java2WSDL to running out of memory? Is this consistently reproduceable?
I haven't been working with the WSDL for a while, but I will come back with the status on the latest version soon. From my point of view - it's the OutOfMemory error that's the problem, the other errors has to wait.
This error still occurs in Eclipse 3.2 and WTP 1.5 (callisto update). This bug allowed no productive work with Wclipse and WTP. In my option the severity is critical. Log: !ENTRY org.eclipse.osgi 2 1 2006-07-03 11:08:13.732 !MESSAGE NLS unused message: LABEL_BUTTON_STOP_WSDL_VALIDATION in: org.eclipse.jst.ws.internal.consumption.ui.ConsumptionUI !ENTRY org.eclipse.osgi 2 1 2006-07-03 11:08:13.732 !MESSAGE NLS unused message: TOOLTIP_STOP_VALIDATION_BUTTON in: org.eclipse.jst.ws.internal.consumption.ui.ConsumptionUI !ENTRY org.eclipse.ui 4 4 2006-07-03 11:14:36.187 !MESSAGE Unhandled event loop exception !ENTRY org.eclipse.ui 4 0 2006-07-03 11:14:36.187 !MESSAGE PermGen space !STACK 0 java.lang.OutOfMemoryError: PermGen space !ENTRY system.bundle 4 0 2006-07-03 11:15:00.362 !MESSAGE FrameworkEvent.ERROR !STACK 0 java.lang.OutOfMemoryError: PermGen space
(In reply to comment #10) > This error still occurs in Eclipse 3.2 and WTP 1.5 (callisto update). This bug > allowed no productive work with Wclipse and WTP. In my option the severity is > critical. Hendrik, which VM are you using? Did you try starting with a greater perm size? ...eclipse.exe ... -vmargs -XX:MaxPermSize=256m
(In reply to comment #11) > Hendrik, which VM are you using? Did you try starting with a greater perm size? > ...eclipse.exe ... -vmargs -XX:MaxPermSize=256m Thanks for your tip, I use jre1.5.0_04.
I am experiencing the similar problems. When editing an Xdoclet EJB (not just xml files, .java files as well) I get sporadic crashes, I may hit enter for a new line, crash. I might hit tab, crash. All crashes produce: java.lang.OutOfMemoryError: PermGen space Dialog open exception: java.lang.OutOfMemoryError: PermGen space Fatal error happened during workbench emergency close. java.lang.OutOfMemoryError: PermGen space I am running Eclipse-3.2 (Callisto) with sun-jdk-1.5.0.7 and all up-to-date patches via update manager. I currently have been running eclipse like so: eclipse -vm /opt/sun-jdk-1.5.0.07/bin/java -XX:MaxPermSize=256m due to the memory leak, with no success. I get this on amd64 and x86, with sun-jdk-1.5 and sun-jdk-1.4 respectively. This is a critical bug, as it crashes every few minutes of use. I will help in any way I can.
ug, I didnt realize this was on the windows platform, my problems are on linux. Should I submit a different bug? Thanks.
cc'ing Jeffrey in hopes that he's herding the various PermGen related bugs.
Brandon, I could not reproduce the problem. Using -XX:MaxPermSize=256m, I have never run into a OOME. My system is RHEL 3, x86, Sun JRE 1.4.2_07. I tried editing a bunch of .xml and .java and WTP is still running fine. Anything special about your .xml and .java files? Would it be possible to post some of them?
Jeffrey, So I added "-vmargs" to my execute line for eclipse, giving: eclipse -vm /opt/sun-jdk-1.5.0.07/bin/java -vmargs -XX:MaxPermSize=256m and I have not had any PermGen errors. It would appear that the maxpermsize wasn't being registered. Everything is running good atm, I will let you know if anything changes. Thanks for the help. Brandon
Jeff, I'm going to assign these memory related bugs over to you.
*** This bug has been marked as a duplicate of 129490 ***
This is part of a mass update to close out all stale WTP bugs which are in the resolved state without an appropriate targeted version. If you feel this bug was closed inappropriately, please reopen.
