Built apps crash on opening with MacOS Ventura

I’m getting many reports from users unable to open my built apps that were working fine before upgrading to Ventura. I tried building with the app with the latest Xojo version (2022 R3), but still crashes on open. The report fragment below is virtually the same for each user case. Unable to duplicate on any owned machine. Very frustrating.

Has anyone seen/resolved this?

//////
ARM-64 (Native) launchd [1]
501
Date/Time: OS Version: Report Version: Anonymous UUID:
Sleep/Wake UUID:
2022-12-02 10:21:11.4791 -0700 macOS 13.0.1 (22A400)
12
F266997D-8B6A-5FD0-258F-05E2B5DFA057 BC7B7D74-A513-4BDE-B24E-B5891AE0B5D5
Time Awake Since Boot: 3000 seconds Time Since Wake: 3059 seconds
System Integrity Protection: enabled
Notes: dyld_process_snapshot_create_for_process failed with 5
Crashed Thread:
Exception Type: Exception Codes: Exception Codes:
Termination Reason: Terminating Process:
0 Dispatch queue: com.apple.main-thread
EXC_BAD_ACCESS (SIGSEGV) KERN_INVALID_ADDRESS at 0x0000000000000000 0x0000000000000001, 0x0000000000000000
Namespace SIGNAL, Code 11 Segmentation fault: 11 exc handler [1280]
VM Region Info: 0 is not in any region. Bytes before following region: 4334338048 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START
—>__TEXT 10258c000-103dc8000 [ 24.2M] r-x/r-x SM=COW …
Error Formulating Crash Report: dyld_process_snapshot_create_for_process failed with 5
Kernel Triage: VM - pmap_enter retried due to resource shortage
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_platform.dylib 1 libsystem_c.dylib 2 libsystem_c.dylib 3 HIToolbox
0x1b0661704 _platform_strlen + 4 0x1b04f9140 __vfprintf + 5080 0x1b0526b98 _vasprintf + 276
0x1b9fbec28 HILogToClient + 44 0x1b9fbf064 HIPrintBacktrace + 44 0x1b9dfb94c MenuBarInstance::EnsureAutoShowObserver() +
4 HIToolbox 5 HIToolbox 120 6 HIToolbox 7 HIToolbox HIApplication::HandleActivated(OpaqueEventRef*, unsigned char, OpaqueWindowPtr*, unsigned char) + 172
0x1b9d9e698 SetMenuBarObscured + 224 0x1b9d9e304
8 HIToolbox OpaqueEventRef*, void*) + 296 9 HIToolbox 10 HIToolbox 11 HIToolbox 12 HIToolbox _BlockUntilNextEventMatchingListInModeWithFilter + 72 13 AppKit 0x1b396c630 _DPSNextEvent + 632 14 AppKit 0x1b396b7c0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 728
0x1b9d983e8 HIApplication::EventObserver(unsigned int,
0x1b9d5f154 _NotifyEventLoopObservers + 176 0x1b9d97d88 AcquireEventFromQueue + 432 0x1b9d87228 ReceiveNextEventCommon + 712 0x1b9d86f48
0x104cb2de4 0x104c24000 + 585188 0x104cb1fc8 CocoaProcessOneEvent(bool) + 272 0x104e34030 ModalEvents(unsigned char) + 76 0x104e48e74 RuntimeShowModalWithinWindow + 356
15 XojoFramework 16 XojoFramework

As a Tester you should try the latest beta, and report at the beta testers area if still crashing. Since R3.0 many things were done.

1 Like

Just a guess: try ShowModal instead of ShowModalWithin…

The latest version is actually 3.2. Maybe you meant this, but you should make sure you’re at least here.

Rick is right about testing on the beta channel. Also, if possible with a secondary machine or VM, also test on macOS betas. I have a Ventura-specific menubar bug that seems to have been fixed at Apple’s end in 13.1.

1 Like

Yes - I inadvertently left the point off. I have built with the latest release as well as the latest beta. I will try looking for ShowModalWithin as Thomas suggested. Thanks.

ShowModalWithin can be used for sure without issues on macOS 13.
But it is important that you do not close the parent window without first closing the Modal window.

This maybe related to Stage Manager.
When you set the settings according the screenshot you get some funky results when using ModalWithin.
If you do the same coded with Xcode, it works fine though. So that maybe a Xojo issue too.

EDIT: sorry, the odd behaviour is also happening with Swift (Xcode).