https://bugs.kde.org/show_bug.cgi?id=520106
--- Comment #1 from [email protected] --- Crash Type: EXC_BAD_ACCESS (SIGSEGV) – Null pointer dereference (KERN_INVALID_ADDRESS at 0x0000000000000000) Thread: Main thread (com.apple.main-thread) Exact Crash Location: Function: QAbstractItemModel::beginInsertRows (QtCore) Context: Triggered by Digikam::AlbumManager::scanPAlbums() → insertPAlbum() → slotAlbumAboutToBeAdded() Root Cause: Likely a NULL pointer in a PAlbum (album pointer) or memory corruption during album insertion. Key Observations Qt Model Notification Issue: The crash occurs when digiKam attempts to notify the UI (via rowsAboutToBeInserted) about album changes. Suggests a race condition or invalid model index in AbstractAlbumModel. Multi-Threading Risk: AlbumManager is accessed by multiple threads (e.g., ScanController thread). The crash happens in the main thread, but concurrent modifications (e.g., from scanPAlbums) may corrupt the model. Database Corruption: digiKam uses SQLite (libsqlite3.0.dylib). A corrupted database (e.g., digikam4.db) could lead to invalid album pointers. Qt 6.10 Potential Bug: digiKam 9.0.0 uses Qt 6.10. Known issues in Qt 6.x with QAbstractItemModel notifications (e.g., QTBUG-114491). ---------- Next stage: please try with digiKam pre-release 9.1.0 which uses Qt 6.11: https://files.kde.org/digikam/ -- You are receiving this mail because: You are watching all bug changes.
