Hi Philippe and WaveLab Team,
I experienced a sudden crash with WaveLab 13 (v13.0.20.1278) on macOS 15.7.7 (Apple Silicon). The application closed unexpectedly during a mouse movement while some plugins were open.
According to the crash log, the crash occurred in the main thread (Thread 0) due to a segmentation fault (EXC_BAD_ACCESS / SIGSEGV) within the Qt layout system, specifically during a UI visibility trigger.
Key lines from the crash log:
- Exception Type: EXC_BAD_ACCESS (SIGSEGV)
- Crashed Thread: 0 Dispatch queue: com.apple.main-thread
- Call Stack:
0 QtWidgets_WL 0x10a9858cc WL::QLayout::activateRecursiveHelper(WL::QLayoutItem*) + 20
1 QtWidgets_WL 0x10a985908 WL::QLayout::activateRecursiveHelper(WL::QLayoutItem*) + 80
2 QtWidgets_WL 0x10a944744 WL::QLayout::activate() + 88
3 QtWidgets_WL 0x10a9a6c4c WL::QWidgetPrivate::setVisible(bool) + 1128
18 QtGui_WL 0x109deb98c WL::QGuiApplicationPrivate::processMouseEvent(...)
It seems like a UI rendering conflict in the updated WaveLab 13 graphics framework. Thanks for looking into this!
Best regards,
Jay