Bug 79398

Summary:

[History] clean-up deletes state files regardless other references exist

Product:

[Eclipse Project] Platform

Reporter:

Rafael Chaves <eclipse>

Component:

Resources

Assignee:

Platform-Resources-Inbox <platform-resources-inbox>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

CC:

Version:

3.1

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
test case	none

Description Rafael Chaves

2004-11-24 10:49:51 EST

i20041123

When cleaning up the history, we are not doing reference counting, so we end up
deleting states for other files as well.

Comment 1 Rafael Chaves

2004-11-24 11:22:03 EST

*** Bug 79357 has been marked as a duplicate of this bug. ***

Comment 2 Rafael Chaves

2004-11-24 13:36:04 EST

This is true for both current and new implementations. The new implementation
made it worse because cleaning (for the destination) was happening on every move
(not mentioning the in-memory collection of removed blobs was being cleared).,
so the source file would end up having states whose blobs were deleted.

Comment 3 Rafael Chaves

2004-11-24 14:33:53 EST

Created attachment 16109 [details]
test case

This seems to be a regression caused by the fix to bug 66369. This test case
fails on both implementations.

Comment 4 John Arthorne

2005-04-29 15:33:57 EDT

Marking 3.2 (unless you want to solve this next week, Rafael ;)

Comment 5 Rafael Chaves

2005-04-29 15:37:08 EDT

*** Bug 93276 has been marked as a duplicate of this bug. ***

Comment 6 Martin Burger

2005-04-29 15:48:15 EDT

Is there any chance of fixing this in 3.1?

Comment 7 Rafael Chaves

2005-04-29 16:07:26 EDT

Chances are slim to none. We have no time left.

Comment 8 Rafael Chaves

2007-02-07 15:51:32 EST

Not an active committer any longer, moving to the inbox...

Comment 9 Eclipse Webmaster

2019-09-06 16:13:17 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.