SUMMARY While editing subtitles, when opening the 'Manage Subtitles' window to make edits to styles, subtitle layers, etc., the moment the window is closed out of, whether pressing the 'Close' button in the bottom right or the 'X' in the top left of the window, the entire application hard crashes and gives a report, with the summary report below. STEPS TO REPRODUCE 1. Open kdenlive. 2. Add a subtitle layer. 3. Select 'Manage Subtitles' from the dropdown on the left side of the subtitle layer. 4. Close out of the window that appears. 5. Application immediately crashes. OBSERVED RESULT Entire program terminates. EXPECTED RESULT 'Manage Subtitles' window expected to close to continue editing. SOFTWARE/OS VERSIONS macOS: Sequoia 15.1.1 Qt Version: 6.7.3 ADDITIONAL INFORMATION: CRASH SUMMARY ------------------------------------- Translated Report ------------------------------------- Process: kdenlive [9640] Path: /Applications/kdenlive.app/Contents/MacOS/kdenlive Identifier: org.kde.Kdenlive Version: 24.12 () Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-01-26 23:24:51.2377 -0500 OS Version: macOS 15.1.1 (24B2091) Report Version: 12 Anonymous UUID: A8932234-11AB-5B30-A68A-AAC983D2D2E3 Time Awake Since Boot: 5900 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000db Exception Codes: 0x0000000000000001, 0x00000000000000db Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [9640] VM Region Info: 0xdb is not in any region. Bytes before following region: 4376805157 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 104e0c000-105718000 [ 9264K] r-x/r-x SM=COW /Applications/kdenlive.app/Contents/MacOS/kdenlive Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 QtCore 0x108b47100 QObject::blockSignals(bool) + 4 1 kdenlive 0x1050742d4 0x104e0c000 + 2523860 2 kdenlive 0x1050743c0 0x104e0c000 + 2524096 3 QtWidgets 0x1086b4d68 QDialog::exec() + 412 4 kdenlive 0x105468cb8 0x104e0c000 + 6671544 5 kdenlive 0x1054870d0 0x104e0c000 + 6795472 6 QtCore 0x108b4eff4 0x108a6c000 + 929780 7 QtCore 0x108b618a0 0x108a6c000 + 1005728 8 QtCore 0x108b46b6c QObject::event(QEvent*) + 104 9 QtWidgets 0x10847c61c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 336 10 QtWidgets 0x10847d5d8 QApplication::notify(QObject*, QEvent*) + 504 11 QtCore 0x108afec0c QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212 12 QtCore 0x108c85edc QTimerInfoList::activateTimers() + 1144 13 libqcocoa.dylib 0x10a1bc1a4 0x10a1a4000 + 98724 14 CoreFoundation 0x182fe1d34 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 15 CoreFoundation 0x182fe1cc8 __CFRunLoopDoSource0 + 176 16 CoreFoundation 0x182fe1a2c __CFRunLoopDoSources0 + 244 17 CoreFoundation 0x182fe05c8 __CFRunLoopRun + 840 18 CoreFoundation 0x182fdfbc4 CFRunLoopRunSpecific + 588 19 HIToolbox 0x18e451f64 RunCurrentEventLoopInMode + 292 20 HIToolbox 0x18e457d54 ReceiveNextEventCommon + 636 21 HIToolbox 0x18e457eb8 _BlockUntilNextEventMatchingListInModeWithFilter + 76 22 AppKit 0x186b0b98c _DPSNextEvent + 660 23 AppKit 0x18744bddc -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688 24 AppKit 0x186afea64 -[NSApplication run] + 480 25 libqcocoa.dylib 0x10a1bcdfc 0x10a1a4000 + 101884 26 QtCore 0x108b09d50 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 1112 27 QtCore 0x108aff430 QCoreApplication::exec() + 136 28 kdenlive 0x104e245fc 0x104e0c000 + 99836 29 dyld 0x182b78274 start + 2840
Thank you for reporting. I can confirm the crash. Following your steps. This seems to be a Mac related issue/crash. That doesn’t happen on Window and Linux.
(In reply to emohr from comment #1) > Thank you for reporting. I can confirm the crash. Following your steps. > > This seems to be a Mac related issue/crash. That doesn’t happen on Window > and Linux. Is this something that should be reported to Apple? I'm not sure what the next steps would be.
Thanks for your report, and no, sending this to Apple won't help. We have confirmed the bug and I just pushed a fix: https://invent.kde.org/multimedia/kdenlive/-/commit/b391a6591cb74967d3bc347aa2a5b0d848ebb9f1 The fix will be in 24.12.2, that will probably be released on the 10th of february.