[SOLVED] Ozone 3.23 - 3.24a not working in OSX

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Ozone 3.23 - 3.24a not working in OSX

    I am also consistently having problems with recent versions of Ozone on OSX.
    I just tried 3.24b, and these issues persisted. I believe they showed up all through the 3.23 series, so I have been using 3.22a.

    - Dragging the "FreeRTOS" window from being docked to undocked will usually result in an app hang or immediate app crash
    - Dragging other windows around sometimes does not cause a crash, but resizes the app window and results in large blank gray spaces in the layout
    - Font looks odd; might be an intentional design change, rather than a bug

    The top of the stack trace looks like this:

    Source Code

    1. Process: Ozone [60080]
    2. Path: /Applications/SEGGER/*/Ozone.app/Contents/MacOS/Ozone
    3. Identifier: com.segger.Ozone.V324b
    4. Version: 0
    5. Code Type: X86-64 (Native)
    6. Parent Process: bash [1255]
    7. Responsible: Terminal [920]
    8. User ID: 503
    9. Date/Time: 2021-07-02 14:39:30.813 -0700
    10. OS Version: macOS 11.4 (20F71)
    11. Report Version: 12
    12. Bridge OS Version: 5.4 (18P4663)
    13. Anonymous UUID: 4AF77D7B-C1D1-4422-E7A6-5CADEB3DEF5E
    14. Sleep/Wake UUID: 4C8CEA14-4F69-4D0B-A703-BB5ECA2978BE
    15. Time Awake Since Boot: 320000 seconds
    16. Time Since Wake: 11000 seconds
    17. System Integrity Protection: enabled
    18. Crashed Thread: 0 Dispatch queue: com.apple.main-thread
    19. Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    20. Exception Codes: EXC_I386_GPFLT
    21. Exception Note: EXC_CORPSE_NOTIFY
    22. Termination Signal: Segmentation fault: 11
    23. Termination Reason: Namespace SIGNAL, Code 0xb
    24. Terminating Process: exc handler [60080]
    25. Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    26. 0 libQtGui.4.8.7.dylib 0x000000013dd9ee23 QDockAreaLayoutInfo::restoreState(QDataStream&, QList<QDockWidget*>&, bool) + 2451
    27. 1 libQtGui.4.8.7.dylib 0x000000013dd9e675 QDockAreaLayoutInfo::restoreState(QDataStream&, QList<QDockWidget*>&, bool) + 485
    28. 2 libQtGui.4.8.7.dylib 0x000000013dd9fc05 QDockAreaLayout::restoreState(QDataStream&, QList<QDockWidget*> const&, bool) + 309
    29. 3 libQtGui.4.8.7.dylib 0x000000013ddc5d0d QMainWindowLayoutState::restoreState(QDataStream&, QMainWindowLayoutState const&) + 797
    30. 4 libQtGui.4.8.7.dylib 0x000000013ddcb641 QMainWindowLayout::restoreState(QDataStream&) + 401
    31. 5 libQtGui.4.8.7.dylib 0x000000013ddc32cf QMainWindow::restoreState(QByteArray const&, int) + 143
    32. 6 com.segger.Ozone.V324b 0x00000001081453c9 CMainWindow::RestoreWindowState(bool, bool, bool) + 265
    33. 7 com.segger.Ozone.V324b 0x00000001080c389e CMainWindow::OnWindowStateUpdateTimeout() + 62
    34. 8 libQtCore.4.8.7.dylib 0x000000013e6cee9c QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2012
    35. 9 libQtCore.4.8.7.dylib 0x000000013e6ca256 QObject::event(QEvent*) + 102
    36. 10 libQtGui.4.8.7.dylib 0x000000013d9d9a0d QApplicationPrivate::notify_helper(QObject*, QEvent*) + 557
    37. 11 libQtGui.4.8.7.dylib 0x000000013d9db013 QApplication::notify(QObject*, QEvent*) + 403
    38. 12 libQtCore.4.8.7.dylib 0x000000013e6b6551 QCoreApplication::notifyInternal(QObject*, QEvent*) + 113
    39. 13 libQtGui.4.8.7.dylib 0x000000013d990f67 QEventDispatcherMacPrivate::activateTimer(__CFRunLoopTimer*, void*) + 199
    40. 14 com.apple.CoreFoundation 0x00007fff206c62b9 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
    41. 15 com.apple.CoreFoundation 0x00007fff206c5dad __CFRunLoopDoTimer + 927
    42. 16 com.apple.CoreFoundation 0x00007fff206c590a __CFRunLoopDoTimers + 307
    43. 17 com.apple.CoreFoundation 0x00007fff206ac4d3 __CFRunLoopRun + 1988
    44. 18 com.apple.CoreFoundation 0x00007fff206ab64c CFRunLoopRunSpecific + 563
    45. 19 com.apple.HIToolbox 0x00007fff288e9ab3 RunCurrentEventLoopInMode + 292
    46. 20 com.apple.HIToolbox 0x00007fff288e9815 ReceiveNextEventCommon + 587
    47. 21 com.apple.HIToolbox 0x00007fff288e95b3 _BlockUntilNextEventMatchingListInModeWithFilter + 70
    48. 22 com.apple.AppKit 0x00007fff22eac6f2 _DPSNextEvent + 864
    49. 23 com.apple.AppKit 0x00007fff22eaaec5 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1364
    50. 24 com.apple.AppKit 0x00007fff22e9d239 -[NSApplication run] + 586
    51. 25 libQtGui.4.8.7.dylib 0x000000013d9927c3 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1779
    52. 26 libQtCore.4.8.7.dylib 0x000000013e6b34c5 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 581
    53. 27 libQtCore.4.8.7.dylib 0x000000013e6b6b8c QCoreApplication::exec() + 188
    54. 28 com.segger.Ozone.V324b 0x000000010830cd6c main + 284
    55. 29 libdyld.dylib 0x00007fff205cff5d start + 1
    Display All
  • Hi apullin,
    There are a number of bugs for OSX in the Ozone v3.2x series.

    Ozone crashing and drawing large gray spaces when you move/resize windows is a known bug that SEGGER has acknowledged over 3 months ago.

    You may be able to change the font if you go to Tools > Preferences > Appearance > Application and select a new font there. There was a bug in an earlier v3.2x version that prevented you from changing the font, but it's been fixed now. At least, it works for me now.

    Here are some relevant threads regarding the bugs in macOS in the v3.2x series:


    Does the Ozone development team plan to put effort into improving the Mac OS version of Ozone? If not, we would like to know so we can seek alternatives. Thanks
  • Hi appulin,

    Thank you for the inquiry.
    The issue is reproducible. We are looking into it.

    danngreen wrote:

    Does the Ozone development team plan to put effort into improving the Mac OS version of Ozone? If not, we would like to know so we can seek alternatives. Thanks
    Yes of course, otherwise there would not be releases with fixes for macOS, no? All reproducible issues are on our bugtracker and will be fixed over time.
    Please note that this is not a support forum. So if you post something here it is possible that it may be overlooked a couple of days as our engineering team will only sweep through the forum when there is time between development, official support and other paid projects. So if you have any blocking bug that is urgent, feel free to open a support ticket as explained in my signature.

    As you can also see from the posts you linked, not everywhere we receive a usable reproducer which makes it indefinitely harder for us to even try to fix a reported issue.
    With macOS things are also simply different than with Windows or Linux as between Catalina and Big Sur many things have changed from a developer perspective and some changes are not even backwards compatible, and we would not like to exclude our customers that are still on Catalina. So fixes may take longer than for other platforms as the testing is simply more complex.

    I understand your frustration but we can also only work with the information and resources that we get.

    Best regards,
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • OK, thank you for confirming MacOS support. We'll be patient.
    I missed the bug report link in your signature, I thought the forum was the place for bug reports. I apologize.
    I'll use that in the future to report bugs. thanks