| ObjectCollectedException [message #38159] |
Fri, 13 December 2002 18:19  |
Eclipse User |
|
|
|
Originally posted by: robin.rosenberg.dewire.kom.s/k/c/
I get ObjectCollectedException from time to time (M3, Mandrake 9). These seem to occur in
every edition, but M3 is (seems) worse. Along with these exceptions the debugger
in eclipse hangs. Screen refresh works, but I can't do anything.
-- robin
!ENTRY org.eclipse.jdt.debug 4 5010 dec 13, 2002 18:53:33.570
!MESSAGE com.sun.jdi.ObjectCollectedException occurred retrieving thread name.
!STACK 0
com.sun.jdi.ObjectCollectedException
at org.eclipse.jdi.internal.MirrorImpl.defaultReplyErrorHandler (MirrorImpl.java:234)
at org.eclipse.jdi.internal.ThreadReferenceImpl.name(ThreadRefe renceImpl.java:271)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.getName( JDIThread.java:827)
at org.eclipse.jdt.internal.debug.ui.JDIModelPresentation.getTh readText(JDIModelPresentation.java:269)
at org.eclipse.jdt.internal.debug.ui.JDIModelPresentation.getTe xt(JDIModelPresentation.java:216)
at org.eclipse.debug.internal.ui.LazyModelPresentation.getText( LazyModelPresentation.java:68)
at org.eclipse.debug.internal.ui.DelegatingModelPresentation.ge tText(DelegatingModelPresentation.java:121)
at org.eclipse.jface.viewers.TreeViewer.doUpdateItem(TreeViewer .java:82)
at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(Ab stractTreeViewer.java:353)
at org.eclipse.jface.viewers.StructuredViewer.updateItem(Struct uredViewer.java:1132)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh (AbstractTreeViewer.java:833)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh (AbstractTreeViewer.java:847)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh (AbstractTreeViewer.java:816)
at org.eclipse.jface.viewers.StructuredViewer$4.run(StructuredV iewer.java:744)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelecti on(StructuredViewer.java:684)
at org.eclipse.jface.viewers.StructuredViewer.refresh(Structure dViewer.java:742)
at org.eclipse.debug.internal.ui.views.launch.LaunchViewer.refr esh(LaunchViewer.java:62)
at org.eclipse.jface.viewers.AbstractTreeViewer.add(AbstractTre eViewer.java:141)
at org.eclipse.jface.viewers.AbstractTreeViewer.add(AbstractTre eViewer.java:162)
at org.eclipse.debug.internal.ui.views.AbstractDebugEventHandle r.insert(AbstractDebugEventHandler.java:74)
at org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHa ndler.doHandleDebugEvents(LaunchViewEventHandler.java:82)
at org.eclipse.debug.internal.ui.views.AbstractDebugEventHandle r$1.run(AbstractDebugEventHandler.java:49)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 1)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:94)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:1424)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :1275)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1435)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1418)
at org.eclipse.core.internal.boot.InternalBootLoader.run(Intern alBootLoader.java:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
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:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
|
|
|
| Re: ObjectCollectedException [message #38193 is a reply to message #38159] |
Fri, 13 December 2002 19:37  |
| Eclipse User |
|
|
|
Originally posted by: jared-eclipse.mn.rr.com
I think the stack trace is a red herring. The code in JDIModelPresentation
handles the exception gracefully and writes the stack trace to the log.
I run on Mandrake 9 and I just had the debugger hang this morning.
Fortunately, it happened while I was debugging the debugger, so I was able
to suspend the Main thread and see what was going on. In my case, the Main
method was stuck in a call to java.io.File#exists() which is called by the
launch config framework to validate the config file before launching.
I don't know why this call would block.
- Jared
Robin Rosenberg wrote:
> I get ObjectCollectedException from time to time (M3, Mandrake 9). These
> seem to occur in
> every edition, but M3 is (seems) worse. Along with these exceptions the
> debugger in eclipse hangs. Screen refresh works, but I can't do anything.
>
> -- robin
|
|
|
| Re: ObjectCollectedException [message #38226 is a reply to message #38193] |
Fri, 13 December 2002 20:24 |
| Eclipse User |
|
|
|
Originally posted by: robin.rosenberg.dewire.kom.s/k/c/
Do you have any information about what file was being accessed?
-- robin
Jared Burns wrote:
> I think the stack trace is a red herring. The code in JDIModelPresentation
> handles the exception gracefully and writes the stack trace to the log.
>
> I run on Mandrake 9 and I just had the debugger hang this morning.
> Fortunately, it happened while I was debugging the debugger, so I was able
> to suspend the Main thread and see what was going on. In my case, the Main
> method was stuck in a call to java.io.File#exists() which is called by the
> launch config framework to validate the config file before launching.
>
> I don't know why this call would block.
>
> - Jared
>
> Robin Rosenberg wrote:
>> I get ObjectCollectedException from time to time (M3, Mandrake 9). These
>> seem to occur in
>> every edition, but M3 is (seems) worse. Along with these exceptions the
>> debugger in eclipse hangs. Screen refresh works, but I can't do anything.
>>
>> -- robin
|
|
|
| Re: ObjectCollectedException [message #38290 is a reply to message #38226] |
Sat, 14 December 2002 02:10 |
| Eclipse User |
|
|
|
Originally posted by: jared-eclipse.mn.rr.com
Yep. The file was a launch configuration file in the workspace metadata -
something like Hello.launch.
- Jared
Robin Rosenberg wrote:
> Do you have any information about what file was being accessed?
>
<snip>
>>
>> I run on Mandrake 9 and I just had the debugger hang this morning.
>> Fortunately, it happened while I was debugging the debugger, so I was
>> able to suspend the Main thread and see what was going on. In my case,
>> the Main method was stuck in a call to java.io.File#exists() which is
>> called by the launch config framework to validate the config file before
>> launching.
<snip>
|
|
|
| Re: ObjectCollectedException [message #38356 is a reply to message #38290] |
Sat, 14 December 2002 15:37 |
| Eclipse User |
|
|
|
Originally posted by: robin.rosenberg.dewire.kom.s/k/c/
Ok, that seems irrelevant. I got it back to a working state by replacing
most stuff I have updated from cooker the last two days. Among the
last libraries removed before the thing started working was libglib2 and
libgk+-x11+.
I also had an error message about failing to initialize drag and drop when
I left the hanging session for a while. I am quite sure I did not try to do
drag-n-drop at the time. Does that give a clue?
-- robin
Jared Burns wrote:
> Yep. The file was a launch configuration file in the workspace metadata -
> something like Hello.launch.
>
> - Jared
>
> Robin Rosenberg wrote:
>> Do you have any information about what file was being accessed?
>>
> <snip>
>>>
>>> I run on Mandrake 9 and I just had the debugger hang this morning.
>>> Fortunately, it happened while I was debugging the debugger, so I was
>>> able to suspend the Main thread and see what was going on. In my case,
>>> the Main method was stuck in a call to java.io.File#exists() which is
>>> called by the launch config framework to validate the config file before
>>> launching.
> <snip>
|
|
|
| Re: ObjectCollectedException [message #38389 is a reply to message #38356] |
Sat, 14 December 2002 17:10 |
| Eclipse User |
|
|
|
Originally posted by: jared-eclipse.mn.rr.com
Robin Rosenberg wrote:
> I also had an error message about failing to initialize drag and drop when
> I left the hanging session for a while. I am quite sure I did not try to
> do drag-n-drop at the time. Does that give a clue?
Not to me. :-/ Sorry.
- Jared
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04637 seconds
] 
Search
Help
Register
Login
Home
