Created attachment 183655 [details] gdb output, always the same SUMMARY Constant crashes STEPS TO REPRODUCE 1. Run the app 2. Start working (translating, editing, pressing the keyboard buttons) 3. SegFault after some time, couldn't notice the pattern OBSERVED RESULT SIGSEGV, Segmentation fault EXPECTED RESULT Not crash, normal work as usual (been using Lokalize for about 10 year now) SOFTWARE/OS VERSIONS kinfo: Operating System: Manjaro Linux KDE Plasma Version: 6.3.6 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 5.10.240-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3470 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti ADDITIONAL INFORMATION See the gdb output in attachment Valgrind output: ==7848== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==7848== Access not within mapped region at address 0x20 ==7848== at 0x6E18922: UnknownInlinedFun (qhash.h:796) ==7848== by 0x6E18922: UnknownInlinedFun (qhash.h:1189) ==7848== by 0x6E18922: QSortFilterProxyModel::parent(QModelIndex const&) const (qsortfilterproxymodel.cpp:2147) ==7848== by 0x412BF0B: UnknownInlinedFun (qabstractitemmodel.h:506) ==7848== by 0x412BF0B: TM::DBFilesModel::updateStats(QModelIndex const&, QModelIndex const&) (dbfilesmodel.cpp:143) ==7848== by 0x6BCBE33: QObject::event(QEvent*) (qobject.cpp:1431) ==7848== by 0x5787C6F: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3303) ==7848== by 0x6B73117: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1106) ==7848== by 0x6B734FA: UnknownInlinedFun (qcoreapplication.cpp:1546) ==7848== by 0x6B734FA: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (qcoreapplication.cpp:1879) ==7848== by 0x6E4ACF7: UnknownInlinedFun (qcoreapplication.cpp:1733) ==7848== by 0x6E4ACF7: postEventSourceDispatch(_GSource*, int (*)(void*), void*) (qeventdispatcher_glib.cpp:246) ==7848== by 0x905487C: g_main_dispatch (gmain.c:3398) ==7848== by 0x9055CD6: UnknownInlinedFun (gmain.c:4249) ==7848== by 0x9055CD6: g_main_context_iterate_unlocked.isra.0 (gmain.c:4314) ==7848== by 0x9055EE4: g_main_context_iteration (gmain.c:4379) ==7848== by 0x6E475E1: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (qeventdispatcher_glib.cpp:399) ==7848== by 0x6B7F4B5: UnknownInlinedFun (qeventloop.cpp:104) ==7848== by 0x6B7F4B5: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (qeventloop.cpp:186) ==7848== by 0x6B777C0: QCoreApplication::exec() (qcoreapplication.cpp:1449) ==7848== by 0x404F974: main (main.cpp:147) ==7848== If you believe this happened as a result of a stack ==7848== overflow in your program's main thread (unlikely but ==7848== possible), you can try to increase the size of the ==7848== main thread stack using the --main-stacksize= flag. ==7848== The main thread stack size used in this run was 8388608. ==7848== ==7848== HEAP SUMMARY: ==7848== in use at exit: 87,153,294 bytes in 1,131,770 blocks ==7848== total heap usage: 25,976,224 allocs, 24,844,454 frees, 7,782,760,959 bytes allocated ==7848== ==7848== LEAK SUMMARY: ==7848== definitely lost: 768 bytes in 3 blocks ==7848== indirectly lost: 119 bytes in 5 blocks ==7848== possibly lost: 6,713,655 bytes in 3,033 blocks ==7848== still reachable: 80,341,704 bytes in 1,127,845 blocks ==7848== of which reachable via heuristic: ==7848== length64 : 1,443,968 bytes in 1,952 blocks ==7848== newarray : 998,440 bytes in 6,325 blocks ==7848== multipleinheritance: 199,024 bytes in 241 blocks ==7848== suppressed: 0 bytes in 0 blocks ==7848== Rerun with --leak-check=full to see details of leaked memory ==7848== ==7848== Use --track-origins=yes to see where uninitialised values come from ==7848== For lists of detected and suppressed errors, rerun with: -s ==7848== ERROR SUMMARY: 1001 errors from 1000 contexts (suppressed: 0 from 0) Segmentation fault (core dumped) valgrind --num-callers=100 lokalize
Should be fixed in 25.08.0 (or at least I reworked this code into something that should not crash). Please tell us if you update (once it's released in a few weeks) and it still crashes.