View Single Post
Old 04-26-2025, 05:29 PM   #24
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,914
Karma: 6120478
Join Date: Nov 2009
Device: many
Okay, I have implemented unique disk cache storage names and cleanup on export and pushed it to master.

If either of you get a chance (after removing the old debug log txt file), please try with current master and multiple instances of Sigil and see if you still get the expired timer debug message.

If this does not work, then the locking is happening someplace else that impacts the cache clearing, not in the Preview storage name.

If that happens, we will try going with no storage name at all for Preview so it becomes an off-the-record style profile.

At worst case we can skip the cache flushing but that would be a last resort.

I have my fingers crossed.
KevinH is offline   Reply With Quote