Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 323544

Summary:

VM Crash when disposing a Zest Graph

Product:

[Eclipse Project] Platform

Reporter:

Johannes Utzig <jutzig.dev>

Component:

SWT

Assignee:

Platform-SWT-Inbox <platform-swt-inbox>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

major

Priority:

CC:

digulla, eclipse.felipe, ericwill, remy.suen

Version:

3.6

Keywords:

triaged

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Bug Depends on:

Bug Blocks:

331208

Attachments:

Description	Flags
Error Report of JVM crash	none

Description Johannes Utzig

2010-08-24 18:00:51 EDT

Build id: 20100617-1415

When a close an Editor containing a Zest based viewer, the whole JVM crashes. I tried this on both a Sun JVM and IcedTea, both JVMs crash when the viewer gets disposed. 
I'm working on Ubuntu(Gtk) 64Bit. I'll attach the error report

Reproducable: always

Steps to reproduce:
1. install Buckminster
2. Right Click on a (Plug-in) Project
3. Select 'Buckminster' -> 'Open Dependency Graph'
4. Close the editor

Comment 1 Johannes Utzig

2010-08-24 18:02:09 EDT

Created attachment 177373 [details]
Error Report of JVM crash

Comment 2 Felipe Heidrich

2010-08-25 09:03:26 EDT

Does it work if you disable accessibility for the desktop ?

Comment 3 Johannes Utzig

2010-08-25 16:41:03 EDT

(In reply to comment #2)
> Does it work if you disable accessibility for the desktop ?

You mean the 'assistive technologies' of the OS? I never had them activated.

Comment 4 Felipe Heidrich

2010-08-26 09:15:47 EDT

(In reply to comment #3)
> (In reply to comment #2)
> > Does it work if you disable accessibility for the desktop ?
> You mean the 'assistive technologies' of the OS? I never had them activated.

Yes, please make sure it is off.
It is possible that it is active by default (or some random reason)

Comment 5 Johannes Utzig

2010-08-26 09:42:39 EDT

I checked it, everything is off

Comment 6 Aaron Digulla

2010-11-26 16:05:59 EST

I just ran into the same issue. Eclipse crashed and left the workspace in a corrupted state. It was impossible to start it again. I had to wipe .metadata and my Eclipse configuration, losing all my project settings, a lot of preferences, etc.

Comment 7 Remy Suen

2010-11-26 16:09:36 EST

(In reply to comment #6)
> I just ran into the same issue.

Can you attach your JVM crash log?

> Eclipse crashed and left the workspace in a
> corrupted state. It was impossible to start it again. I had to wipe .metadata
> and my Eclipse configuration, losing all my project settings, a lot of
> preferences, etc.

What happened when you tried to start on the same workspace?

Comment 8 Aaron Digulla

2010-11-26 16:17:58 EST

(In reply to comment #7)

> > I just ran into the same issue.
> Can you attach your JVM crash log?

This happened at work; I'll revisit this on Monday.

> > Eclipse crashed and left the workspace in a
> > corrupted state. It was impossible to start it again. I had to wipe .metadata
> > and my Eclipse configuration, losing all my project settings, a lot of
> > preferences, etc.
> 
> What happened when you tried to start on the same workspace?

I got a deadlock while Eclipse loaded the plugins. As far as I could tell, several threads were waiting for a lock that the main thread kept. The splash screen got to about 90% and then stopped. The output was "Loading workbench." There was no useful output on the console nor could I find anything in the OSGi console.

Is there a document how I can debug Eclipse's startup?

Comment 9 Remy Suen

2010-11-26 16:19:03 EST

(In reply to comment #8)
> Is there a document how I can debug Eclipse's startup?

Well, if it appears to be hung, getting a thread dump is usually useful to see what it's doing (if anything).
http://wiki.eclipse.org/index.php/How_to_report_a_deadlock

Comment 10 Eric Williams

2018-04-10 15:30:00 EDT

This code no longer runs on GTK3, as accessibility is implemented differently there.