SUMMARY Sometimes kdenlive crashes and I have to terminate the $PID of the appimage via a konsole. After that it is not possible to find out what caused the crash or if a resource was maxed out. STEPS TO REPRODUCE 1. kdenlive crashes - how can a standard kdenlive user find out afterwards what happened to possibly report a bug? OBSERVED RESULT * atm I have not clue where to look to or how to find out something EXPECTED RESULT * maybe a folder where logfiles on the important tasks are written i.e. proxy file creation, rendering, runtime events SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-27-amd64 (64-bit) Graphics Platform: offscreen Processors: 12 × 13th Gen Intel® Core™ i7-1370P Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics
Thank you for reporting. If you don’t mind, I change the bug to wishlist. Yes, the idea of a crash logger is on our to-do list. It’s difficult to implement such logger without hitting the performance too much. Maybe we can run a “hidden” terminal to log all actions which could help to find the bug. But this is not the same as running a debugger when the crash has happened. Important are the steps you have made leading to the crash.
(In reply to emohr from comment #1) > Thank you for reporting. If you don’t mind, I change the bug to wishlist. > Yes, the idea of a crash logger is on our to-do list. It’s difficult to > implement such logger without hitting the performance too much. > > Maybe we can run a “hidden” terminal to log all actions which could help to > find the bug. But this is not the same as running a debugger when the crash > has happened. > > Important are the steps you have made leading to the crash. maybe it would also be an option, to enable / disable this logging so that if a project leads repeatedly to a crash, you can switch it on and try to "catch" the issue.. I agree it is just a "wish" with low prio for me and maybe most users too..