https://bugs.kde.org/show_bug.cgi?id=379669
RJVB <rjvber...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #105432|0 |1
is obsolete| |
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
Created attachment 105591
--> https://bugs.kde.org/attachment.cgi?id=105591&action=edit
my current test patch
This elaborates on the previous versions by shadowing m_dirty during the
finalCleanup call. IIUC, that flag indicates whether the repository was dirtied
since the last call to finalCleanup (final? :)) . Ensuring that nothing can
touch that flag while finalCleanup runs seems thus a constructive idea.
Also, don't break out of the inner loop if Bucket::deleteItem bails out early.
Either the two changes might have prevented my latest hang where deleteItem was
called repeatedly with the same index and item hash from the Type repository.
A thought: could those unexpected items represent stale items that weren't
removed properly? Is there a way to know what the item is/was at this location?
--
You are receiving this mail because:
You are watching all bug changes.
