Known Issues
Beta Status
Phosor is currently in an Internal Beta stage. Features may change before the public release. Performance may occasionally be inconsistent depending on hardware, image formats, and library size. Unexpected bugs may still occur. Feedback from beta testers is highly appreciated.
This page lists known behaviors (intentional design decisions) and potential bugs that may have edge cases requiring additional testing.
Known Behaviors
These behaviors are intentional and should not be reported as bugs:
1. Zoom resets on navigation
Zoom and pan state reset to defaults (50% zoom, centered) when navigating to a new photo. This is by design to ensure each photo starts from a consistent viewing state.
2. Navigation wraps around
Pressing → on the last photo returns to the first, and pressing ← on the first photo goes to the last. This allows continuous sorting without reaching a dead end.
3. Duplicate sort advances
If a photo is already assigned to a category and you press that category's key again, the photo simply advances without creating a new history entry.
4. All actions blocked during Execute
Navigation, sorting, undo/redo, and burst mode are blocked while files are being moved. This prevents state corruption during the move operation.
5. Category configuration resets on restart
Categories, colors, keybindings, and output folders are not persisted between sessions. Each launch starts with two default categories.
6. Debug toasts in development mode
In development mode, additional "[DEBUG]" toast notifications appear for every action. These are suppressed in release builds.
7. Context menu disabled
Right-click context menus are disabled across the application to prevent interference with the sorting workflow.
8. Source path preserved on empty folder
If you select a folder with no supported files, the source path in the sidebar continues showing the previous valid folder. The current photo list and application state remain unchanged.
9. Burst mode auto-disables on category deletion
If a category is deleted while it's the active burst key, burst mode is automatically stopped.
10. Single toast at a time
Only one toast notification is visible at a time. New toasts immediately replace the current one.
Possible Bugs
These areas may have edge cases that deserve additional testing:
1. Large JPEG files
Very large JPEG files may cause memory spikes. See Performance for details.
2. Cross-device move edge cases
Moving files between different filesystems (e.g., from an external drive to the internal drive) may take longer. Verify file integrity after cross-device moves.
3. Rapid mode toggling
Rapidly toggling Continue Mode while a burst is active may leave the burst in an inconsistent state. Test toggling mid-burst.
4. Metadata for corrupted EXIF
Files with corrupted or partial EXIF data may cause metadata loading to fail silently. Verify graceful degradation.
5. Very long category names
Category names that exceed the sidebar width should truncate gracefully. Test with very long names.
6. Undo history overflow
After 100 undo entries, the oldest entry is discarded. Verify that the history remains consistent after overflow.
7. Concurrent folder changes
Rapidly changing the source folder while a scan is in progress may cause unexpected behavior. Wait for the scan to complete before switching folders.
8. Empty output folder on execute
Executing a move when all flagged categories have output folders set, but one folder doesn't exist yet — verify the folder is created automatically.