Archicad 29.2 crashing on MAc

[Brad Elliott]

I upgraded to 29.2 and had multiple crashes in multiple different files doing randomly different things. I gave up and went back to 29.1 which is working fine. Anybody else having issues with the latest update? I am on an M5 Macbook Pro.

Operating system used: Mac Apple Silicon 26.5 Tahoe

[moalali]

We can confirm this issue. Multiple users in our office (architecture firm, ~mixed Apple Silicon (M3,M5) fleet) are seeing random crashes with Archicad 29.2.0 GER (Build 5003) on macOS 26.5.2 (Tahoe).

I analyzed the macOS crash reports and they consistently show the same pattern: EXC_BAD_ACCESS (SIGSEGV) / KERN_INVALID_ADDRESS with a "possible pointer authentication failure", crashing on the main thread in Graphisoft's dialog library:

Thread 0 Crashed:: CrBrowserMain0 libobjc.A.dylib objc_msgSend + 321 DG -[DGCDial windowWillEnterFullScreen:] + 162 CoreFoundation __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148

So in our case the trigger is a window entering macOS full screen mode — a DG dialog object that was already deallocated is still registered as an NSNotificationCenter observer and gets called during the fullscreen transition (use-after-free). This would explain why the crashes appear "random": it depends on which dialogs/palettes were opened and closed before the transition.

Workaround that helps here: avoid the macOS full screen mode (green traffic light button / own Space) while working. We are also considering rolling back to 29.1, which others in this thread report as stable.

Reported to Graphisoft support with Incident Identifier EA87B488-D3F6-48D5-B44C-8A124970A2D6. Would be great to get an official statement or hotfix timeline.

[Fabio Ferrini]

Since updating to Archicad 29.2.0 build 5003 ITA FULL, we have been experiencing frequent Teamwork synchronization failures with BIMcloud as a Service.

Hardware and software environment:
Mac mini 2024, Apple M4 processor, 32 GB RAM, running macOS Sequoia 15.5.

During normal work, Archicad reports that it cannot synchronize the Teamwork project with the server and offers the option to save the project locally. However, the local saving procedure never completes successfully.

When the project is reopened or recovered, it only contains the state of the most recent successful Send & Receiveoperation. All subsequent local modifications are missing.

This problem has occurred repeatedly in our office since the latest update and has caused the loss of several hours of work. The recovery option offered by Archicad does not preserve the unsent changes stored in the local Teamwork data.

Please investigate this as a serious data-loss issue and advise whether the unsent local modifications can be recovered from the Teamwork cache.