yeah no thanks! I'll stick with 28.2 and native comp on my macbook for now 😄

Doom on latest --HEAD --with-native-comp on M1 Mac randomly would die for me. That's always super unexpected and extremely annoying. I couldn't figure out the cause. I'm currently using GNU Emacs 30.0.50 without native-comp, and I'm not noticing any lags. Ironically, since I update Doom and Emacs fairly often, on native-comp it would have to re-compile things, and while it does it, things would get noticeably laggy. So it really is the opposite for me - native-comp Emacs is slower. After many months of preaching about how great the native-comp is (on Intel-Mac I felt the difference), with M1, now, I'm quite convinced - it doesn't hold up to the hype.

I've had a good experience tracking emacs-29 on Apple M1/M2 with native-comp. It's been stable and fast for me. I use macports for all my deps (texinfo, gccjit, etc). I build stock emacs-29 branch with --

export NATIVE_FULL_AOT=1 CFLAGS="-O2 -Wl,-rpath,/opt/local/lib/gcc12/"
sh autogen.sh
./configure --with-ns --with-native-compilation --with-tree-sitter=/opt/local --with-xwidgets
make -j12 bootstrap && make tags && make install

(not sure if the -Wl,-rpath stuff is necessary any more.. that might be a quirk of my macports install)

I also use MacPorts, but in my case emacs-app package with the +imagemagick variant so that pdf-tools plays nicely with the high DPI displays on my work laptop. Still, after running for a few days, the most random operations will trigger a segfault, typically when using treemacs on a large project. I never see this happen on other platforms

I heard about the "disable native-comp" suggestion from old coworkers who would use some Emacs package from Homebrew and default to using an alternative package with it disabled in order to stop crashing on M1 macs

emacs-plus 29.0.90 with native comp on m1 is very stable for me

I never had a build of 29 crash on me on osx so far