When I open baangt UI on Mac and close it (either via close from the top window or via Exit-Button) I get a segmentation fault.
Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [75670] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 QtWidgets 0x0000000124813a1a QBoxLayoutPrivate::deleteAll() + 186 1 QtWidgets 0x0000000124815757 QHBoxLayout::~QHBoxLayout() + 39 2 QtWidgets.abi3.so 0x00000001144dbdd8 non-virtual thunk to sipQHBoxLayout::~sipQHBoxLayout() + 56 3 QtWidgets 0x0000000124813a1d QBoxLayoutPrivate::deleteAll() + 189 4 QtWidgets 0x0000000124815be7 QVBoxLayout::~QVBoxLayout() + 39 5 QtWidgets.abi3.so 0x00000001144d9747 sipQVBoxLayout::~sipQVBoxLayout() + 55 6 QtWidgets 0x000000012482a4f7 QWidget::~QWidget() + 407 7 QtWidgets.abi3.so 0x000000011445ab07 sipQGroupBox::~sipQGroupBox() + 55 8 QtCore 0x00000001256a72a4 QObjectPrivate::deleteChildren() + 228 9 QtWidgets 0x000000012482a74e QWidget::~QWidget() + 1006 10 QtWidgets.abi3.so 0x00000001144f7987 sipQWidget::~sipQWidget() + 55 11 QtCore 0x00000001256a72a4 QObjectPrivate::deleteChildren() + 228 12 QtWidgets 0x000000012482a74e QWidget::~QWidget() + 1006 13 QtWidgets.abi3.so 0x00000001143f7b77 sipQStackedWidget::~sipQStackedWidget() + 55 14 QtCore 0x00000001256a72a4 QObjectPrivate::deleteChildren() + 228 15 QtWidgets 0x000000012482a74e QWidget::~QWidget() + 1006 16 QtWidgets.abi3.so 0x00000001144f7987 sipQWidget::~sipQWidget() + 55 17 QtCore 0x00000001256a72a4 QObjectPrivate::deleteChildren() + 228 18 QtWidgets 0x000000012482a74e QWidget::~QWidget() + 1006 19 QtWidgets.abi3.so 0x0000000114437037 sipQMainWindow::~sipQMainWindow() + 55
Resolved! It was the exiting method in ui which was causing this error.
When I open baangt UI on Mac and close it (either via close from the top window or via Exit-Button) I get a segmentation fault.
Resolved! It was the exiting method in ui which was causing this error.