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

Bug 331372

Summary:	eclipse.stateSaveDelayInterval is set to 0 causes large number of old cache files
Product:	[Eclipse Project] Equinox	Reporter:	Thomas Watson <tjwatson>
Component:	Framework	Assignee:	equinox.framework-inbox <equinox.framework-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	dimitar.giormov, l.kirchev
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Thomas Watson

2010-11-29 14:05:32 EST

When running with eclipse.stateSaveDelayInterval=0 a large number of framework cache generation files will be created (e.g. .bundledata.1, .bundledata.2 ...).

This is because we only clean up old generations when closing the framework.  Some other approach for clean up should be considered when using eclipse.stateSaveDelayInterval=0 setting.

Comment 1 Eclipse Genie

2019-11-06 09:28:21 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.

--
The automated Eclipse Genie.