-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Furnace built on macOS 14 crashes when using previous versions of macOS (especially in old processors) #1952
Comments
Oh no... this is the second time I get a crash on the very startup... Mac and CPU model? |
Mac Pro early 2009, Xeon CPU (X5690, i think). GPU is a Radeon VII. |
Try using latest artifact. This one in particular. |
I get the same result with the latest artifact. It still crashes. The Furnace icon appears for a second, vanishes, and the MacOS Problem Report dialogue appears. |
Try with this one: https://github.com/tildearrow/furnace/actions/runs/9587807739 It is built in macOS 12 (which was used by builds before 0.6.3). |
That works! Thank you. |
hm. macOS 10.15.7 Catalina 🥹 MacBook Pro 2017, Intel Core i7 here is output of 0.6.3:
|
Reset your configuration file. The Metal backend is experimental and no longer the default in 0.6.4. |
Thanks. The build you linked yesterday in this thread works for me. |
Dropping Critical priority since macOS 12 is being used for the builds. The issue remains with macOS 14 though. |
macOS 12 image is going to be removed soon. I will test whether we still can build with macOS 13 and have it work. |
Try using this artifact: https://github.com/tildearrow/furnace/actions/runs/11713850806 It is built under macOS 13. |
The linked artifact works for me. |
Great! Let's use macOS 13 for now. |
Furnace version 0.6.4 is crashing on MacOS Big Sur (11.7.9) immediately upon loading. I deleted the configs, but that didn't fix the issue. I have attached a copy of the error message. The last version of Furnace that seems to work for me is 0.6.2...
furnace_crash_log.txt
The text was updated successfully, but these errors were encountered: