(2021 R1 MacOS ARM-64 IDE) 64509 - IDE on Apple arm-64 crashes when moving the IDE window

Feedback Case Number: 64509
Feedback Case URL: <https://xojo.com/issue/64509>
Feedback Case Title: 64509 - IDE on Apple arm-64 crashes with datecontrol (IDE crashes)

We have sudden crashes in the IDE this seems to happen alot on a daily basis since 2021 R1 on MacOS ARM-64 Big Sur systems. This crash is so dooming that when working with 2021 R1 we are unable to continue for longer than 20 minutes using this version any longer on Native ARM-64.

Crash happens if the IDE window is moved (dragged) or something is changed on anther screen for example. The report seems to indicate something to do with moving the IDE window but we’re not sure what’s the actual problem. Here is the crash report:

Xojo: Xojo 2021r1

Steps: On (2021 R1) a MacBook Pro M1 the IDE constantly crashes out of the blue with this log:

Process: Xojo [2344]
Path: /Applications/Xojo 2021 Release 1/Xojo.app/Contents/MacOS/Xojo
Identifier: com.xojo.xojo
Version: (
Code Type: ARM-64 (Native)
Parent Process: ??? [1]
Responsible: Xojo [2344]
User ID: 501

Date/Time: 2021-04-20 16:51:04.921 +0200
OS Version: macOS 11.2.3 (20D91)
Report Version: 12
Anonymous UUID: E6A5F401-2D34-6E27-18C5-9835E4CCF568

Sleep/Wake UUID: 72AAC9FD-CDCB-45EA-86C9-0CE8D338926A

Time Awake Since Boot: 1100 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010

VM Regions Near 0x10:
__TEXT 100acc000-10adf8000 [163.2M] r-x/r-x SM=COW /Applications/Xojo 2021 Release 1/Xojo.app/Contents/MacOS/Xojo

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 b7fzRx.DateControl.dylib 0x0000000298b1d29c DateControl_Destroy(REALobjectStruct*) + 144
1 b7fzRx.DateControl.dylib 0x0000000298b1d248 DateControl_Destroy(REALobjectStruct*) + 60
2 PluginBridgeCocoa.dylib 0x000000010bf3a5e8 0x10bf28000 + 75240
3 com.xojo.xojo 0x0000000100d2fcd4 PluginControlInstance.__exit%%o + 68
4 com.xojo.XojoFramework 0x000000010c2aa2a8 RuntimeUnlockObject + 732
5 com.xojo.xojo 0x0000000101ad6e4c PainterWindow.PainterWindow.Rebuild%%o<PainterWindow.PainterWindow> + 2480
6 com.xojo.xojo 0x0000000106437c8c UniversalLayoutEditor.UniversalLayoutEditor.OwningWindowDidMove%%o<UniversalLayoutEditor.UniversalLayoutEditor> + 1012
7 com.xojo.xojo 0x0000000105c0d58c StudioMainEditor.StudioMainEditor.OwningWindowDidMove%%o<StudioMainEditor.StudioMainEditor> + 384
8 com.xojo.xojo 0x0000000104887ea8 StudioMainWindow.StudioMainWindow.Event_Moved%%o<StudioMainWindow.StudioMainWindow> + 1100
9 com.xojo.xojo 0x0000000101423fbc DocWindow.Event_Moved%%o + 140
10 com.apple.CoreFoundation 0x000000018c5655a8 CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 28
11 com.apple.CoreFoundation 0x000000018c6067d4 ___CFXRegistrationPost_block_invoke + 52
12 com.apple.CoreFoundation 0x000000018c606740 _CFXRegistrationPost + 440
13 com.apple.CoreFoundation 0x000000018c534090 _CFXNotificationPost + 720
14 com.apple.Foundation 0x000000018d29d650 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
15 com.apple.AppKit 0x000000018ed9dc4c -[NSWindow _setFrameCommon:display:fromServer:] + 2308
16 com.apple.AppKit 0x000000018eecde48 -[NSWindow _windowMovedToRect:] + 144
17 com.apple.AppKit 0x000000018eecdc88 -[NSWindow _windowMoved:] + 820
18 com.apple.AppKit 0x000000018eecd918 -[NSWindow _internalHandleAppKitDefinedEvent:] + 272
19 com.apple.AppKit 0x000000018eeccdb0 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 3472
20 com.apple.AppKit 0x000000018eecbdb4 -[NSWindow(NSEventRouting) sendEvent:] + 352
21 com.xojo.XojoFramework 0x000000010c13fa58 0x10c0a0000 + 653912
22 com.apple.AppKit 0x000000018eecae8c -[NSApplication(NSEvent) sendEvent:] + 3328
23 com.xojo.XojoFramework 0x000000010c12f928 0x10c0a0000 + 588072
24 com.xojo.xojo 0x0000000100b9ef8c Application._CallFunctionWithExceptionHandling%%op + 164
25 com.xojo.XojoFramework 0x000000010c2a7a1c CallFunctionWithExceptionHandling(void (*)()) + 180
26 com.xojo.XojoFramework 0x000000010c12f8d8 0x10c0a0000 + 587992
27 com.apple.AppKit 0x000000018f19a46c -[NSApplication _handleEvent:] + 76
28 com.apple.AppKit 0x000000018ed39088 -[NSApplication run] + 640
29 com.xojo.XojoFramework 0x000000010c2a62fc RuntimeRun + 48
30 com.xojo.xojo 0x0000000100cb3840 REALbasic._RuntimeRun + 28
31 com.xojo.xojo 0x000000010ab754c0 _Main + 384
32 com.xojo.xojo 0x000000010ab4f898 main + 20
33 libdyld.dylib 0x000000018c491f34 start + 4

Are you sure you have latest DateControl ?

The crash log shows very old issue that was fixed many months ago. It was issue in porting to ARM which I could not isolate at first while I was waiting to get access to M1 Mac, then it got fixed in begin of December.

We have installed the latest plugin controls including datecontrol.
Do we need the others too? Typelib etc to be the latest?

Xojo is stable here with DateControl on M1. Just the computer is not stable.

1 Like

So and you use 2021R1 natively eg non-rosetta?


Thanks, we’ll try some more. It would be great if @Björn_Eiríksson has it’s plugins in a complete package including the dependend plugins where there was a list of fixes like MBS has.

It does not crash here.

MacBook Pro 8/512
Xojo 2021r1
Big Sur 11.2.3

There is no dependent plugin.

If you go in Help ‚Üí Plugins inside Xojo then what version does it say ?

DateControl 9.2.0 current and was the same with 2020R2.1 we used.
So the version number has not changed on your plugin?

Plugin version was 8.5.0 on 2021R1 previously when crashing.

I do not know what you mean by version number has not changed.

9.2 is latest version.

I have been hammering it back and forth in the IDE and like the others am not able to crash it. That does not mean it does not crash. There could be some setting on it maybe that the others do not have, and I am not thinking of when testing.

Maybe post snaps of the property settings you got on the control you think is crashing ?

Or make empty project and drag date control on it and does that crash for you ?

DateControl 9.2.0 current and was the same with 2020R2.1 we used.
So the version number has not changed on your plugin?

exuse, we had 8.5.0 installed previously. Not 9.2.0. So it could be the plugin being the cause.

8.5 has the issue from before December yes.

We are currently still testing if this is the actual cause, we’ll be using the ide for today with the newer plugins to see if this fixed the issue.
Thanks @Björn_Eiríksson and @Beatrix_Willius for the info.

1 Like