Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » Execution Time Analysis Fails Due To OutOfMemoryException

Home » Archived » Test and Performance Tools Platform (TPTP) » Execution Time Analysis Fails Due To OutOfMemoryException

Execution Time Analysis Fails Due To OutOfMemoryException [message #81756]

Fri, 25 August 2006 11:39

Eclipse User

Originally posted by: wolfgang.rohregger.mci.edu

Hi!

I'm trying to profile an Eclipse RCP application. The app is using
hibernate to connect to a database. At some point (the one I want to
profile) it starts fetching huge amounts of data from the db. During
non-profiling execution a heap space of up to 1.5 GB is required at this
point. After this it should only require between 700 - 1500 MB.
Now then trying to make an Execution Time Analysis on the app
(specifically only including the top level package of one plugin) the
profiling aborts at the point where it should start loading tons of data
from the db:

2006-08-25 17:23:55,640 ERROR [main] (FunErrorDialog.java:168) -
Migrationsfehler-Migration fehlgeschlagen:null
java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.run(ModalContext.ja va:350)
at
org.eclipse.jface.dialogs.ProgressMonitorDialog.run(Progress MonitorDialog.java:479)
at edu.mci.fun.migration.MigrationView.migrate(MigrationView.ja va:314)
at edu.mci.fun.migration.MigrationView.access$1(MigrationView.j ava:278)
at
edu.mci.fun.migration.MigrationView$2.widgetSelected(Migrati onView.java:269)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2968)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at edu.mci.fun.gui.FunStartup.run(FunStartup.java:97)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
Caused by: java.lang.OutOfMemoryError: Java heap space

The documentation states somewhere that when profiling apps with much
data, one should profile to a file. I set this in the Profiling
Execution Dialog, in the tab called "Destination".
This didn't help either.

How would I profile the application even though it's producing a huge
amount of objects/data/method calls?

Best regards,

Wolfgang Rohregger

Re: Execution Time Analysis Fails Due To OutOfMemoryException [message #81896 is a reply to message #81756]

Tue, 29 August 2006 05:51

Eclipse User

Originally posted by: wolfgang.rohregger.mci.edu

Wolfgang Rohregger schrieb:
> Hi!
>
> I'm trying to profile an Eclipse RCP application. The app is using
> hibernate to connect to a database. At some point (the one I want to
> profile) it starts fetching huge amounts of data from the db. During
> non-profiling execution a heap space of up to 1.5 GB is required at this
> point. After this it should only require between 700 - 1500 MB.
> Now then trying to make an Execution Time Analysis on the app
> (specifically only including the top level package of one plugin) the
> profiling aborts at the point where it should start loading tons of data
> from the db:

VM Parameters seem to be ignored by profile launch configuration:
"-Xms1024m -Xmx1600m".

The VM of the application only gets 64M instead of 1600M.

Could this be a bug?

Best regards,

Wolfgang Rohregger

Previous Topic:	Can TPTP provides Java Call Graph?
Next Topic:	firefox and tptp

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 02:29:32 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter