Final Stability Update for 2025 · Release Candidate 42 and 43

On the UI side, the film strip controls in both the details view and related files popup have been adjusted for better visibility with the new always visible scroll bars.

One of the more significant improvements involves how metadata and thumbnail caches are structured in new libraries. We've increased the size of metadata and cache fragments, which reduces the number of files kept open simultaneously during operation. This change helps lower system resource pressure, particularly on setups with large libraries or limited file descriptor availability. It also contributes to better recovery behavior after unexpected crashes, which ties into another fix: we’ve resolved an issue where a large number of cache entries could be lost following a crash. This will result in faster reinitialization after interruptions.

Library handling has also seen several targeted fixes. A regression affecting the display of remote file status in scanned folders has been corrected, ensuring accurate synchronization state reporting. Additionally, we’ve addressed a race condition that could allow two library maintenance tasks to run in parallel – an issue that could lead to inconsistent states and extended wait times.

A number of crash fixes improve robustness during edge-case interactions. These include crashes triggered during dialog opening while heavy asset loading is in progress, during standby mode while cloning, and when attempting to drag non-local files into keyword trees. We’ve also resolved a crash that could occur when loading an older catalog format while other instances of the same library are active on the network – a scenario that may occur when plugging in an external drive with a library instance after a longer time.

Another subtle but important fix prevents library instance settings from being reset if the application terminates mid-clone. This could be a significant issue in combination with the previously crash issue of the application crashing when the system is put into standby mode.

Lastly, we’ve mitigated a low-level issue on some systems where the application could fail to start with a “failed to create event” error—typically related to OS-level event handling limits.

As always, see the change log for the full list of changes.

Update 2025/12/22 – Release Candidate 43

It turned out that the increased thumbnail cache file size of RC 42 lead to a regression that caused a crash when cloning large libraries. RC 43 fixes this issue, as well as some secondary issues that were discovered in relation to this.

See the change log for the full list of changes.