Community
Participate
Working Groups
i20041123 When cleaning up the history, we are not doing reference counting, so we end up deleting states for other files as well.
*** Bug 79357 has been marked as a duplicate of this bug. ***
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.
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.
Marking 3.2 (unless you want to solve this next week, Rafael ;)
*** Bug 93276 has been marked as a duplicate of this bug. ***
Is there any chance of fixing this in 3.1?
Chances are slim to none. We have no time left.
Not an active committer any longer, moving to the inbox...
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.