Continuous crashes on 2022r3.1

Hi all.
With the latest version, on Apple M1 with Ventura, Xojo 2022r3.1 keeps crashing! Upon opening, two out of three times it crashes, after two or three times I compile an application it crashes … Impossible to work like this! If we also consider that when it opens it takes two minutes … Really tiring!
Is there anything you can do to fix these annoying problems?

2022r3.2 was released today. Can you try that?

1 Like

Surely! Here is night now, I will check tomorrow morning! Let’s hope!

I’m not see these problems. There was a few items but 3.2 is fixed. When does it crash? I’ve a large project and it loads fast and runs happily. Do you use plug-ins? If so make sure you update to the latest version, that fixed a lot of issues.

1 Like

I’m getting the same problem with r3.1 and r3.2 on Ventura 13.0, including latest MBS plugins (22.5).

Apple details:


Translated Report (Full Report Below)

Process: Xojo [1426]
Path: /Applications/Xojo 2022 Release 3.2/Xojo.app/Contents/MacOS/Xojo
Identifier: com.xojo.xojo
Version: 22.3.2.58445 (22.3.2.3.58445)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2022-11-08 18:15:15.9456 -0500
OS Version: macOS 13.0 (22A380)
Report Version: 12
Anonymous UUID: F4E70C63-DAB1-1C3B-57A9-2CF76A1A66A6

Time Awake Since Boot: 240 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 0x0000000000000030
Exception Codes: 0x0000000000000001, 0x0000000000000030

VM Region Info: 0x30 is not in any region. Bytes before following region: 105557277016016
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
MALLOC_NANO (reserved) 6000f8000000-600100000000 [128.0M] rw-/rwx SM=NUL …(unallocated)

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 dyld 0x1a3c4298c lsl::PersistentAllocator::processDeallocationChain() + 216
1 dyld 0x1a3c429bc lsl::PersistentAllocator::processDeallocationChain() + 264
2 dyld 0x1a3c42b2c lsl::PersistentAllocator::deallocate_buffer(lsl::Allocator::Buffer) + 36
3 dyld 0x1a3c23be0 dyld4::RuntimeState::commitProcessSnapshot() + 136
4 dyld 0x1a3c238e0 dyld4::RuntimeState::notifyDebuggerLoad(std::__1::span<dyld4::Loader const*, 18446744073709551615ul> const&) + 92
5 dyld 0x1a3c52f3c dyld4::APIs::dlopen_from(char const*, int, void*)::$_0::operator()() const + 748
6 dyld 0x1a3c4c968 dyld4::APIs::dlopen_from(char const*, int, void*) + 892
7 PluginBridgeCocoa.dylib 0x110a08b14 0x110a00000 + 35604
8 PluginBridgeCocoa.dylib 0x110a0abf8 0x110a00000 + 44024
9 PluginBridgeCocoa.dylib 0x110a09d30 0x110a00000 + 40240
10 PluginBridgeCocoa.dylib 0x110a06b88 0x110a00000 + 27528
11 Xojo 0x10091cc78 PluginBridge.LoadPlugin%b%oo + 96
12 Xojo 0x10390c87c RBLibrary.LoadOnePlugin%o%obb + 4396
13 Xojo 0x1039dc6d4 RBLibrary.LoadPluginsFromFolder%%ooA1obb + 2304
14 Xojo 0x1039de30c RBLibrary.LoadUserPlugins%%o + 1512
15 Xojo 0x1038daf44 RBLibrary.Load%%o + 10100
16 Xojo 0x1009659e0 IDEApp.Event_Open%%o + 64312
17 XojoFramework 0x10cc488d0 CocoaFinishApplicationStartup() + 184
18 XojoFramework 0x10cc47404 0x10cb64000 + 930820
19 CoreFoundation 0x1a401658c CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 148
20 CoreFoundation 0x1a40b4074 ___CFXRegistrationPost_block_invoke + 88
21 CoreFoundation 0x1a40b3fbc _CFXRegistrationPost + 440
22 CoreFoundation 0x1a3fe7bac _CFXNotificationPost + 708
23 Foundation 0x1a4ed472c -[NSNotificationCenter postNotificationName:object:userInfo:] + 88
24 AppKit 0x1a727fa1c -[NSApplication _postDidFinishNotification] + 284
25 AppKit 0x1a727f7cc -[NSApplication _sendFinishLaunchingNotification] + 172
26 AppKit 0x1a72789d4 _DPSNextEvent + 1564
27 AppKit 0x1a72777c0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 728
28 XojoFramework 0x10cc491f0 0x10cb64000 + 938480
29 XojoFramework 0x10cc49278 0x10cb64000 + 938616
30 Xojo 0x100709328 Application._CallFunctionWithExceptionHandling%%op + 164
31 XojoFramework 0x10cdd33d4 CallFunctionWithExceptionHandling(void (*)()) + 180
32 XojoFramework 0x10cc49214 0x10cb64000 + 938516
33 AppKit 0x1a726bbf0 -[NSApplication run] + 464
34 XojoFramework 0x10cdd1c30 RuntimeRun + 48
35 Xojo 0x10086f0ac REALbasic._RuntimeRun + 28
36 Xojo 0x10aea2a30 _Main + 384
37 Xojo 0x10ae7cf44 main + 20
38 dyld 0x1a3c17e50 start + 2544

Certainly looks like a plug-in issue. I don’t use them, which explains the difference.

@Christian_Schmitz am I correct?

Worth reading this:

I removed all plugins and tried again. Still crashes.

Also did a clean install of Ventura and ran disk utility first aid. Still crashes.

Could be all manor of things, I understand the actual crash to say that Xojo is being terminated for accessing an object that either doesn’t exist or is outside of it’s memory space.

I know you need to be careful with functions that use char for paths, but I would imagine an error earlier in the chain.

The crash was occurring before any projects were loaded, so unless it was something to do with recent files?

I removed a whole gaggle of older Login items in system preferences, restarted and now Xojo has loaded OK (well twice, so it might be early to tell).

1 Like

Yeah, it’s occurring in the loading of dynamic libraries (which don’t have to be Xojo plugin’s as there are various dynamic libraries on the system that an application could utilize), which is occurring during launch.

If it’s randomly occurring, it is probably another Apple bug, Xojo might be able to narrow down the trigger or potentially use alternative API, in this case, they may even be able to use the private API instead of the public API.

Do Xojo made applications also crash?

Not so far. But they do have other problems.

Apple: That 60% of developers who’re unhappy developing for our platforms, are delusional.

You do still have a Monterey partition you can boot back into right? If not, then I suggest you check out how to create a new APFS volume and install the next macOS into that when it ships, so you can avoid things like this.

Yes, I usually don’t install the first version out - why did I do it this time? I don’t know but my ■■■ has been bitten.

Yes, I’ll reinstall Monterey (if possible) and a new partition for Ventura.

Ooo, that’s interesting, my slightly rude word has been bleeped out! Cool, ish.

a$$?

Have you set the Build Architecture as ARM 64 bit or Universal ?
If “ARM 64 bit” changing it to “Universal” (usual default) causes any difference?

Edit: That’s Xojo, not an App. Doh! Maybe some caches need to be erased?

This crash is part of macOS Ventura.
We reported it to Apple and await a fix in a .1 or .2 update.

And no idea why you guys installed Ventura without such a bug fix update.

Because Apple released it, so Apple says it’s ready to go.

Also I found out with Sleep Aid, that some people don’t even know when their Mac updates. A bit more research found that in some cases Apple will update your machine overnight.

13.1 is already in beta, so maybe 13.2, 13.3, 13.4, .5 or 14. It doesn’t appear to affect Apple’s apps, so it’s not a priority.

Well, in the past the release had to go out due to hardware being ready, which requires it.

So all .0 updates ship with plenty of bugs and Apple quickly provides a .1 or .2 to fix the most urgent ones.
And I don’t see how we could do something about dlopen() bugs from our side. it randomly crashes.

1 Like