Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331372 - eclipse.stateSaveDelayInterval is set to 0 causes large number of old cache files
Summary: eclipse.stateSaveDelayInterval is set to 0 causes large number of old cache f...
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-29 14:05 EST by Thomas Watson CLA
Modified: 2019-11-06 09:28 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Watson CLA 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 CLA 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.