out of memory with 2.0.1 [message #200751] |
Sun, 30 September 2007 11:04  |
Eclipse User |
|
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_000C_01C80383.FAD71D60
Content-Type: text/plain;
format=flowed;
charset="windows-1255";
reply-type=original
Content-Transfer-Encoding: 7bit
Hi,
I just installed the 2.0.1 build and began getting out of memory errors too
often.
I've seen this issue in bugzilla, but It seemed to me like it was an old
issue that was resolved a long time ago. Maybe this is a new bug with the
same symptoms.
Attaching a log snippet.
------=_NextPart_000_000C_01C80383.FAD71D60
Content-Type: application/octet-stream;
name=".log"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename=".log"
!SESSION 2007-09-30 16:37:29.343 =
-----------------------------------------------
eclipse.buildId=3DM20070921-1145
java.version=3D1.6.0_02
java.vendor=3DSun Microsystems Inc.
BootLoader constants: OS=3Dwin32, ARCH=3Dx86, WS=3Dwin32, NL=3Den_US
Command-line arguments: -os win32 -ws win32 -arch x86 -data =
D:\work\eclipse workspaces\ws3
!ENTRY org.eclipse.core.resources 2 1 2007-09-30 16:47:20.703
!MESSAGE Skipping builder 'net.sourceforge.metrics.builder' for project =
'Renderer'. Either the builder is missing from the install, or it =
belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.wst.server.core 4 0 2007-09-30 16:47:49.125
!MESSAGE Error calling delegate setDefaults() ServerWorkingCopy =
9_30_07_4_47_PM0
!STACK 0
java.lang.NullPointerException
at =
org.eclipse.jst.server.generic.core.internal.GenericServer.g etServerDefin=
ition(GenericServer.java:239)
at =
org.eclipse.jst.server.generic.core.internal.GenericServer.s etDefaults(Ge=
nericServer.java:324)
at =
org.eclipse.wst.server.core.internal.ServerWorkingCopy.setDe faults(Server=
WorkingCopy.java:608)
at =
org.eclipse.wst.server.core.internal.ServerType.createServer (ServerType.j=
ava:195)
at =
org.eclipse.wst.server.ui.internal.wizard.page.ServerCreatio nCache.getSer=
ver(ServerCreationCache.java:61)
at =
org.eclipse.wst.server.ui.internal.wizard.page.NewManualServ erComposite.l=
oadServerImpl(NewManualServerComposite.java:214)
at =
org.eclipse.wst.server.ui.internal.wizard.page.NewManualServ erComposite.h=
andleTypeSelection(NewManualServerComposite.java:383)
at =
org.eclipse.wst.server.ui.internal.wizard.page.NewManualServ erComposite$1=
..serverTypeSelected(NewManualServerComposite.java:123)
at =
org.eclipse.wst.server.ui.internal.viewers.ServerTypeComposi te$2.selectio=
nChanged(ServerTypeComposite.java:85)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:857)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:19 9)
at =
org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer .java:160)
at =
org.eclipse.jface.viewers.StructuredViewer.updateSelection(S tructuredView=
er.java:2047)
at =
org.eclipse.jface.viewers.StructuredViewer.setSelection(Stru cturedViewer.=
java:1641)
at =
org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer .java:1095)
at =
org.eclipse.wst.server.ui.internal.viewers.ServerTypeComposi te.setVisible=
(ServerTypeComposite.java:97)
at =
org.eclipse.wst.server.ui.internal.wizard.page.NewManualServ erComposite.s=
etVisible(NewManualServerComposite.java:407)
at =
org.eclipse.wst.server.ui.internal.wizard.page.NewServerComp osite.createC=
ontrol(NewServerComposite.java:233)
at =
org.eclipse.wst.server.ui.internal.wizard.page.NewServerComp osite. <init>(=
NewServerComposite.java:121)
at =
org.eclipse.wst.server.ui.internal.wizard.fragment.NewServer WizardFragmen=
t.createComposite(NewServerWizardFragment.java:74)
at =
org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.cre ateControl(Ta=
skWizardPage.java:43)
at =
org.eclipse.wst.server.ui.internal.wizard.TaskWizard.createP ageControls(T=
askWizard.java:396)
at =
org.eclipse.jface.wizard.WizardDialog.createPageControls(Wiz ardDialog.jav=
a:669)
at =
org.eclipse.jface.wizard.WizardDialog.createContents(WizardD ialog.java:54=
3)
at org.eclipse.jface.window.Window.create(Window.java:426)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1081)
at org.eclipse.jface.window.Window.open(Window.java:785)
at =
org.eclipse.wst.server.ui.internal.actions.LaunchWizardActio n.run(LaunchW=
izardAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
at =
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(Act=
ionContributionItem.java:546)
at =
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributi=
onItem.java:490)
at =
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContr=
ibutionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at =
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:2=
89)
at =
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:46=
1)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at =
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplicati=
on.java:106)
at =
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.ja=
va:169)
at =
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplicati=
on(EclipseAppLauncher.java:106)
at =
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(Eclips=
eAppLauncher.java:76)
at =
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:3=
63)
at =
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:1=
76)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
!ENTRY org.eclipse.jdt.core 4 4 2007-09-30 16:48:05.203
!MESSAGE JavaBuilder handling ImageBuilderInternalException while =
building: Formatter
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Problems =
encountered while deleting resources.
at =
org.eclipse.core.internal.resources.Resource.delete(Resource .java:713)
at =
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.clea nOutputFolder=
s(BatchImageBuilder.java:111)
at =
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.buil d(BatchImageB=
uilder.java:45)
at =
org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(J avaBuilder.ja=
va:269)
at =
org.eclipse.jdt.internal.core.builder.JavaBuilder.build(Java Builder.java:=
183)
at =
org.eclipse.core.internal.events.BuildManager$2.run(BuildMan ager.java:624=
)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at =
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.jav=
a:166)
at =
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.jav=
a:197)
at =
org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:246=
)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at =
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.jav=
a:249)
at =
org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager=
..java:302)
at =
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:334=
)
at =
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBu ildJob.java:1=
37)
at =
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJ ob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 org.eclipse.core.resources 4 273 2007-09-30 16:48:05.203
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 2 org.eclipse.core.resources 4 273 2007-09-30 16:48:05.203
!MESSAGE Could not delete '/Formatter/build/classes/com'.
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Problems =
encountered while deleting resources.
at =
org.eclipse.core.internal.localstore.FileSystemResourceManag er.delete(Fil=
eSystemResourceManager.java:223)
at =
org.eclipse.core.internal.resources.ResourceTree.internalDel eteFolder(Res=
ourceTree.java:351)
at =
org.eclipse.core.internal.resources.ResourceTree.standardDel eteFolder(Res=
ourceTree.java:782)
at =
org.eclipse.core.internal.resources.Resource.unprotectedDele te(Resource.j=
ava:1659)
at =
org.eclipse.core.internal.resources.Resource.delete(Resource .java:700)
at =
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.clea nOutputFolder=
s(BatchImageBuilder.java:111)
at =
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.buil d(BatchImageB=
uilder.java:45)
at =
org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(J avaBuilder.ja=
va:269)
at =
org.eclipse.jdt.internal.core.builder.JavaBuilder.build(Java Builder.java:=
183)
at =
org.eclipse.core.internal.events.BuildManager$2.run(BuildMan ager.java:624=
)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at =
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.jav=
a:166)
at =
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.jav=
a:197)
at =
org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:246=
)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at =
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.jav=
a:249)
at =
org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager=
..java:302)
at =
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:334=
)
at =
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBu ildJob.java:1=
37)
at =
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJ ob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 3 org.eclipse.core.resources 4 273 2007-09-30 16:48:05.203
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 4 org.eclipse.core.filesystem 4 273 2007-09-30 16:48:05.203
!MESSAGE Problems encountered while deleting files.
!SUBENTRY 5 org.eclipse.core.filesystem 4 273 2007-09-30 16:48:05.203
!MESSAGE Could not delete: D:\work\eclipse =
workspaces\ws3\Formatter\build\classes\com\sundaysky.
!SUBENTRY 5 org.eclipse.core.filesystem 4 273 2007-09-30 16:48:05.203
!MESSAGE Could not delete: D:\work\eclipse =
workspaces\ws3\Formatter\build\classes\com.
!SUBENTRY 3 org.eclipse.core.filesystem 4 273 2007-09-30 16:48:05.203
!MESSAGE Problems encountered while deleting files.
!SUBENTRY 4 org.eclipse.core.filesystem 4 273 2007-09-30 16:48:05.203
!MESSAGE Could not delete: D:\work\eclipse =
workspaces\ws3\Formatter\build\classes\com\sundaysky.
!SUBENTRY 4 org.eclipse.core.filesystem 4 273 2007-09-30 16:48:05.203
!MESSAGE Could not delete: D:\work\eclipse =
workspaces\ws3\Formatter\build\classes\com.
!ENTRY org.eclipse.ui 4 0 2007-09-30 16:56:13.812
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.OutOfMemoryError: Java heap space
!ENTRY org.eclipse.core.jobs 4 2 2007-09-30 16:56:13.812
!MESSAGE An internal error occurred during: "Requesting Java AST from =
selection".
!STACK 0
java.lang.OutOfMemoryError: Java heap space
------=_NextPart_000_000C_01C80383.FAD71D60--
|
|
|
|
|
|
|
|
|
|
|
Re: out of memory with 2.0.1 [message #200992 is a reply to message #200951] |
Tue, 02 October 2007 07:16   |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------020707060402050505060800
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Zohar,
Running out of permgen space (I think) is typically related to having
lots of .class files and lots of string constants so while the default
setting may be fine for Eclipse with JDT, if you load lots more plugins
it might not be fine. For my purposes (working with bare Eclipse along
with about 150 modeling plugins) I've never needed to change the base
settings. It would certainly seem helpful if the wiki of known issues
talked about this particular issue.
<http://wiki.eclipse.org/SDK_Known_Issues#Windows_issues>
http://wiki.eclipse.org/SDK_Known_Issues#Windows_issues
Issues related to heap or permgen space seem to be a daily occurrence on
the platform or newcomers newsgroups. I'm also not sure if the packaged
download change these default settings...
So while you could open a bugzilla, you might also contribute to the wiki...
zohar wrote:
> If this is so obvious, why isn't it set like that in the eclipse.ini
> which comes out of the box? Should I open a bugzilla issue for that?
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:fdqn55$h8f$1@build.eclipse.org...
>> Zohar,
>>
>> If you run out of PermGen space, make the last number bigger. If you
>> run out of heap memory again make the 512 bigger.
>>
>>
>> zohar wrote:
>>> I have this now:
>>>
>>> "C:\Program Files\eclipse\eclipse.exe" -vmargs -Xms128m -Xmx512m
>>> -XX:MaxPermSize=128m
>>>
>>> Should this be OK?
>>>
>>> <user@domain.invalid> wrote in message
>>> news:fdqljs$d9a$1@build.eclipse.org...
>>>> Ed Merks wrote:
>>>>> Zohar,
>>>>>
>>>>> Likely you'll want to double or more the -Xmx256m value.
>>>>>
>>>>>
>>>>> zohar wrote:
>>>>>> Here it is...
>>>>>>
>>>>>> "Konstantin Komissarchik" <kosta@bea.com> wrote in message
>>>>>> news:fdohfo$oh6$1@build.eclipse.org...
>>>>>>> How much memory are you allocating to eclipse? What does your
>>>>>>> eclipse.ini look like?
>>>>>>>
>>>>>>> - Konstantin
>>>> WTP on less than 512m is a NO GO at least with all WTP-projects I
>>>> have created!
>>>> - Göran Rehnlund
>>>
--------------020707060402050505060800
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Zohar,<br>
<br>
Running out of permgen space (I think) is typically related to having
lots of .class files and lots of string constants so while the default
setting may be fine for Eclipse with JDT, if you load lots more plugins
it might not be fine. For my purposes (working with bare Eclipse along
with about 150 modeling plugins) I've never needed to change the base
settings. It would certainly seem helpful if the wiki of known issues
talked about this particular issue. <a
href="http://wiki.eclipse.org/SDK_Known_Issues#Windows_issues"><br>
</a>
<blockquote><a
href="http://wiki.eclipse.org/SDK_Known_Issues#Windows_issues">http://wiki.eclipse.org/SDK_Known_Issues#Windows_issues</a><br>
</blockquote>
Issues related to heap or permgen space seem to be a daily occurrence
on the
platform or newcomers newsgroups. I'm also not sure if the packaged
download change these default settings...<br>
<br>
So while you could open a bugzilla, you might also contribute to the
wiki...<br>
<br>
<br>
zohar wrote:
<blockquote cite="mid:fdsoma$tvc$1@build.eclipse.org" type="cite">If
this is so obvious, why isn't it set like that in the eclipse.ini which
comes out of the box? Should I open a bugzilla issue for that?
<br>
<br>
"Ed Merks" <a class="moz-txt-link-rfc2396E" href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> wrote in message
<a class="moz-txt-link-freetext" href="news:fdqn55$h8f$1@build.eclipse.org">news:fdqn55$h8f$1@build.eclipse.org</a>...
<br>
<blockquote type="cite">Zohar,
<br>
<br>
If you run out of PermGen space, make the last number bigger. If you
run out of heap memory again make the 512 bigger.
<br>
<br>
<br>
zohar wrote:
<br>
<blockquote type="cite">I have this now:
<br>
<br>
"C:\Program Files\eclipse\eclipse.exe" -vmargs -Xms128m -Xmx512m
-XX:MaxPermSize=128m
<br>
<br>
Should this be OK?
<br>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:user@domain.invalid"><user@domain.invalid></a> wrote in message
<a class="moz-txt-link-freetext" href="news:fdqljs$d9a$1@build.eclipse.org">news:fdqljs$d9a$1@build.eclipse.org</a>...
<br>
<blockquote type="cite">Ed Merks wrote:
<br>
<blockquote type="cite">Zohar,
<br>
<br>
Likely you'll want to double or more the -Xmx256m value.
<br>
<br>
<br>
zohar wrote:
<br>
<blockquote type="cite">Here it is...
<br>
<br>
"Konstantin Komissarchik" <a class="moz-txt-link-rfc2396E" href="mailto:kosta@bea.com"><kosta@bea.com></a> wrote in message
<a class="moz-txt-link-freetext" href="news:fdohfo$oh6$1@build.eclipse.org">news:fdohfo$oh6$1@build.eclipse.org</a>...
<br>
<blockquote type="cite">How much memory are you allocating
to eclipse? What does your eclipse.ini look like?
<br>
<br>
- Konstantin
<br>
</blockquote>
</blockquote>
</blockquote>
WTP on less than 512m is a NO GO at least with all WTP-projects I have
created!
<br>
- Göran Rehnlund
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
</blockquote>
<br>
</body>
</html>
--------------020707060402050505060800--
|
|
|
Re: out of memory with 2.0.1 [message #201016 is a reply to message #200992] |
Tue, 02 October 2007 08:46  |
Eclipse User |
|
|
|
Ed Merks wrote:
> Zohar,
>
> Running out of permgen space (I think) is typically related to having
> lots of .class files and lots of string constants so while the default
> setting may be fine for Eclipse with JDT, if you load lots more plugins
> it might not be fine. For my purposes (working with bare Eclipse along
> with about 150 modeling plugins) I've never needed to change the base
> settings. It would certainly seem helpful if the wiki of known issues
> talked about this particular issue.
> <http://wiki.eclipse.org/SDK_Known_Issues#Windows_issues>
>
> http://wiki.eclipse.org/SDK_Known_Issues#Windows_issues
>
> Issues related to heap or permgen space seem to be a daily occurrence on
> the platform or newcomers newsgroups. I'm also not sure if the packaged
> download change these default settings...
>
> So while you could open a bugzilla, you might also contribute to the wiki...
>
Along with what Ed said, the PermGen issue is SUN JRE specific. Other
JRE's like IBM's or BEA's don't have this particular issue, as they
handle the PermGen space differently. I believe their is already a bug
report opened at Sun's website in regards to the PermGen issue.
>
> zohar wrote:
>> If this is so obvious, why isn't it set like that in the eclipse.ini
>> which comes out of the box? Should I open a bugzilla issue for that?
>>
>> "Ed Merks" <merks@ca.ibm.com> wrote in message
>> news:fdqn55$h8f$1@build.eclipse.org...
>>> Zohar,
>>>
>>> If you run out of PermGen space, make the last number bigger. If you
>>> run out of heap memory again make the 512 bigger.
>>>
>>>
>>> zohar wrote:
>>>> I have this now:
>>>>
>>>> "C:\Program Files\eclipse\eclipse.exe" -vmargs -Xms128m -Xmx512m
>>>> -XX:MaxPermSize=128m
>>>>
>>>> Should this be OK?
>>>>
>>>> <user@domain.invalid> wrote in message
>>>> news:fdqljs$d9a$1@build.eclipse.org...
>>>>> Ed Merks wrote:
>>>>>> Zohar,
>>>>>>
>>>>>> Likely you'll want to double or more the -Xmx256m value.
>>>>>>
>>>>>>
>>>>>> zohar wrote:
>>>>>>> Here it is...
>>>>>>>
>>>>>>> "Konstantin Komissarchik" <kosta@bea.com> wrote in message
>>>>>>> news:fdohfo$oh6$1@build.eclipse.org...
>>>>>>>> How much memory are you allocating to eclipse? What does your
>>>>>>>> eclipse.ini look like?
>>>>>>>>
>>>>>>>> - Konstantin
>>>>> WTP on less than 512m is a NO GO at least with all WTP-projects I
>>>>> have created!
>>>>> - Göran Rehnlund
>>>>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03900 seconds