Stability and Data Safety Improvements · Release Candidate 51+52

Workspace and File Handling Refinements

The workspace view now handles variant detection more intelligently. When a newly detected variant of an original file is identified, it will automatically replace the original in the workspace—provided no other variants have been established yet. This streamlines the user experience by presenting the most relevant version without manual intervention.

Memory Management and Crash Reporting

Memory-related application restarts have been reclassified as crashes, enabling crash report generation for debugging excessive memory consumption. This change gives developers better visibility into memory pressure issues. Additionally, the memory overuse threshold has been recalibrated to prevent unnecessary restarts on systems with 8 GB of RAM or less, reducing disruption for users on modest hardware configurations.

Data Persistence Improvements (macOS/Linux)

On macOS and Linux, the application now writes metadata/thumbnail cache files and library catalog files directly to disk. This mitigates the risk of data loss on non-journaling file systems when system crashes occur or external drives are improperly disconnected. While most modern systems use journaling file systems, this change provides an additional safety net for users on legacy or specialized setups.

Format-Specific Fixes

Several crash scenarios have been addressed: PSD files with corrupted compatibility image data, truncated EXIF data in JXL and PSD files, and edge cases involving zero-pixel images or non-image files in details view. A precision issue affecting grayscale images with bit depths greater than 8-bit has also been resolved, ensuring full tonal range is preserved during processing.

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

2026-05-19: Release Candidate 52

This is a tiny maintenance release that fixes an additional issue with the memory usage watchdog that caused bogus memory overuse errors on some Windows machines.