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

Bug 331246

Summary:	Eclipse should be more robust
Product:	[Eclipse Project] Platform	Reporter:	Aaron Digulla <digulla>
Component:	Runtime	Assignee:	platform-runtime-inbox <platform-runtime-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	remy.suen
Version:	4.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Aaron Digulla

2010-11-26 16:13:52 EST

Build Identifier: 3.6.1 release

When crashing, Eclipse's configuration and metadata can become corrupted. There are several problems:

1. Preferences and caches are mixed. If they were in distinct places (like all preferences must be in one directory and the caches in another), it would be possible to wipe the caches if they are corrupt.

2. Some preferences are only saved to disk when Eclipse is closed. Instead, any changes to the preferences should be saved immediately. This includes:

- Open/close projects
- Settings in the preferences dialog
- Changes in the option menus (like the layout of the JUnit view, layout of the packages in the Package Explorer, etc)

If you want to make this really resilient, save the prefs with a date. When Eclipse is started the next time and it fails, offer a dialog to go back to a stable state. That would also help to debug such problems because reporters could send in a diff.

Reproducible: Always

Comment 1 Eclipse Webmaster

2019-09-06 16:10:59 EDT

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.