Skip to content
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

How can I run Aegisub on M1? #117

Open
Animenosekai opened this issue Aug 4, 2021 · 15 comments
Open

How can I run Aegisub on M1? #117

Animenosekai opened this issue Aug 4, 2021 · 15 comments

Comments

@Animenosekai
Copy link

I just came across your fork and wanted to try it out because the upstream repo isn't maintained anymore.

I'm currently on Apple Silicon and wish to run Aegisub.

The thing is that I tried running r9178, r9198, the GitHub Actions artifact and the latest release version through Rosetta but didn't seem to work, crashing right when I try to open it:

Process:               aegisub [61684]
Path:                  /Applications/Aegisub.app/Contents/MacOS/aegisub
Identifier:            com.aegisub.aegisub
Version:               9178-dev-ec89ce941 (1)
Code Type:             X86-64 (Translated)
Parent Process:        ??? [1]
Responsible:           aegisub [61684]
User ID:               501

Date/Time:             2021-08-04 02:50:35.782 +0200
OS Version:            macOS 11.2.3 (20D91)
Report Version:        12
Anonymous UUID:        2F73CD71-04B2-8CDC-C36A-5B584B294C8A

Sleep/Wake UUID:       8887130F-1334-478C-8071-66A805850E0B

Time Awake Since Boot: 640000 seconds
Time Since Wake:       20000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.Metal.DeviceDispatch

Exception Type:        EXC_BAD_INSTRUCTION (SIGABRT)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
*** Terminating app due to uncaught exception 'NSGenericException', reason: '-[NSAlert runModal] may not be invoked inside of transaction begin/commit pair, or inside of transaction commit (usually this means it was invoked inside of a view's -drawRect: method.)'
BUG IN CLIENT OF LIBDISPATCH: trying to lock recursively
abort() called
terminating with uncaught exception of type NSException

[... long traceback ...]

I don't really care if it runs through Rosetta or natively (just saw #77 but Rosetta doesn't seem to work for me? Maybe I'm doing something wrong?)

Thank you in advance

@hthm00
Copy link

hthm00 commented Aug 5, 2021

Reopen works for me. Have you tried doing so?

@Animenosekai
Copy link
Author

@hthm00
Reopen works for me. Have you tried doing so?

Oh, when the crash report comes? Yea I tried, but it doesn't work, keeps crashing

@hthm00
Copy link

hthm00 commented Aug 12, 2021

Hmm, how about deleting this folder ~/Library/Application Support/Aegisub
Then open Aegisub, when it crashes, hit Reopen

@Animenosekai
Copy link
Author

Hmm, how about deleting this folder ~/Library/Application Support/Aegisub
Then open Aegisub, when it crashes, hit Reopen

Still crashing...

Here is the message from hitting Reopen about 3 times

Process:               aegisub [49195]
Path:                  /Applications/Aegisub.app/Contents/MacOS/aegisub
Identifier:            com.aegisub.aegisub
Version:               9198-dev-4df5f61a5 (1)
Code Type:             X86-64 (Translated)
Parent Process:        ??? [1]
Responsible:           aegisub [49195]
User ID:               501

Date/Time:             2021-08-14 20:18:31.433 +0200
OS Version:            macOS 11.2.3 (20D91)
Report Version:        12
Anonymous UUID:        2F73CD71-04B2-8CDC-C36A-5B584B294C8A

Sleep/Wake UUID:       5F3F624F-E58E-420B-8B88-4511273F7A17

Time Awake Since Boot: 1100000 seconds
Time Since Wake:       4900 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.Metal.DeviceDispatch

Exception Type:        EXC_BAD_INSTRUCTION (SIGABRT)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
*** Terminating app due to uncaught exception 'NSGenericException', reason: '-[NSAlert runModal] may not be invoked inside of transaction begin/commit pair, or inside of transaction commit (usually this means it was invoked inside of a view's -drawRect: method.)'
BUG IN CLIENT OF LIBDISPATCH: trying to lock recursively
abort() called
terminating with uncaught exception of type NSException
[...]

@djwudi
Copy link

djwudi commented Sep 10, 2021

I'm having this same issue on an M1 Mac Mini -- Aegisub 3.3.2 starts to launch, bounces a couple times in the dock, and then dies.

I was happy to find this fork, since it looks like the main Aegisub project has been abandoned, so fingers crossed that this can be figured out.

@Animenosekai
Copy link
Author

I'm having this same issue on an M1 Mac Mini -- Aegisub 3.3.2 starts to launch, bounces a couple times in the dock, and then dies.

I was happy to find this fork, since it looks like the main Aegisub project has been abandoned, so fingers crossed that this can be figured out.

Yea that's exactly what happens to me... Still having my fingers crossed 🤞

@codeman38
Copy link

I'm currently experiencing this on macOS 12.0.1. Reopening worked for me under macOS 11, but it keeps crashing for me under 12 even when I reopen.

@frozenpandaman
Copy link

frozenpandaman commented Nov 8, 2021

I provided a bit more info in my issue above (which was a duplicate, so I closed it, whoops).

Really hoping this can be fixed!! Weirdly the "official" 3.2.2 release still works (…why?!) – but of course it's from 2014, and buggy and unstable…

Edit: @XStylus' comment #77 (comment) points out the r8942 build at http://plorkyeran.com/aegisub/ does work on M1 Macs – it's from 2018, so a bit better than the 2014 one at least (no dark mode though, ha).

@frozenpandaman
Copy link

frozenpandaman commented Nov 8, 2021

Compiling all the posts about this, in case it's helpful:

#117 – How can I run Aegisub on M1?
#77 – Universal Binary for macOS 11
#104 – Tips for building under macOS
#124 – Crashing on M1 Macs
#97 – macOS m1 chip crashes directly when opened and does not work
Aegisub#256 – Is it possble for a Apple Silicon native build?
TypesettingTools#138 – Mac dmg build
TypesettingTools#145 – [macOS] [M1] Build fails
Ristellise/AegisubDC#39 – macOS support?

@WhiredPlanck
Copy link

Regarding this, I've read a Stack Overflow's article that try to answer how to detect the architecture and build the target. The related source is here: https://github.com/axr/solar-cmake/blob/master/TargetArch.cmake . Hope this can help you. CC @wangqr

@Animenosekai
Copy link
Author

Edit: @XStylus' comment #77 (comment) points out the r8942 build at http://plorkyeran.com/aegisub/ does work on M1 Macs – it's from 2018, so a bit better than the 2014 one at least (no dark mode though, ha).

This build does work for me 👍

@frozenpandaman
Copy link

In case it helps anyone:

https://gist.github.com/frozenpandaman/92a84cd2ba690bb2399afd04e695bf8c

@XStylus
Copy link

XStylus commented Mar 17, 2022

I dunno what changed, but wangqr's build of Aegisub 3.3.2 and r9198 appear to be running (or at least launching) after an update to MacOS 12.3.

I have not performed any exhaustive testing beyond just launching the program as of yet.

@codeman38
Copy link

Can confirm what XStylus reports - wangqr's build works for me now after upgrading to macOS 12.3.

@frozenpandaman
Copy link

@XStylus @codeman38 Thanks! Huh, that's odd – works for me too. I really do wonder what changed. Wonder if that means the TypesettingTools builds will work too. I'll make a note of this in my Gist as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants