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

Bug 368369

Summary:

Eclipse fails to start

Product:

[Eclipse Project] Platform

Reporter:

Deepak Azad <deepakazad>

Component:

Assignee:

Platform-UI-Inbox <Platform-UI-Inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

remy.suen

Version:

4.2

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
log	none
deltas.xml	none

Description Deepak Azad

2012-01-11 12:09:52 EST

Created attachment 209321 [details]
log

I20111216-1500

Similar to bug 345623.

After a crash Eclipse failed to restart and the log contains this message - "!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.core.internal.refresh.RefreshJob"

The log also contained some other exceptions. I am attaching the log.

I deleted deltas.xml to resolve the issue.

Comment 1 Deepak Azad

2012-01-11 12:11:25 EST

Created attachment 209323 [details]
deltas.xml

Comment 2 Remy Suen

2012-01-11 14:24:51 EST

The crash must have removed your windows in some strange ways. Based on your model, your root application has no model windows in it.

Comment 3 Deepak Azad

2012-01-11 14:37:30 EST

> The crash must have removed your windows in some strange ways.
Yeah, immediately after the Eclipse crash the OS (Win 7) started behaving in an odd manner and I had to reboot my machine. So the Eclipse crash could have been an OS related issue. (It had been several days since I had rebooted the OS)

> Based on your model, your root application has no model windows in it.
Can Eclipse check for faulty models? And then discard them if this is the case? I don't mind losing the workbench layout as long as Eclipse starts...

Comment 4 Lars Vogel

2019-11-14 03:49:31 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.