You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if it's related to Big Sur or the M1, but on my new MacBook Pro (macOS 11.4), Max (8.1.11) crashes the moment the manta object is instantiated.
The text was updated successfully, but these errors were encountered:
Yup I know about it. I think it's M1. Any chance you can help me test on
the M1 chip with a new build?
On Sat, Jul 24, 2021 at 11:41 AM Damon Holzborn ***@***.***> wrote:
I don't know if it's related to Big Sur or the M1, but on my new MacBook
Pro (macOS 11.4), Max (8.1.11) crashes the moment the manta object is
instantiated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#47>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGAY7DBOPCEHG3A6ASKI6TTZLNK5ANCNFSM5A5SVPFQ>
.
On Jul 24, 2021, at 1:46 PM, Jeff Snyder ***@***.***> wrote:
Yup I know about it. I think it's M1. Any chance you can help me test on
the M1 chip with a new build?
On Sat, Jul 24, 2021 at 11:41 AM Damon Holzborn ***@***.***>
wrote:
> I don't know if it's related to Big Sur or the M1, but on my new MacBook
> Pro (macOS 11.4), Max (8.1.11) crashes the moment the manta object is
> instantiated.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#47>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAGAY7DBOPCEHG3A6ASKI6TTZLNK5ANCNFSM5A5SVPFQ>
> .
>
--
Composer, musician, instrument designer
snyderphonics.com * @snyderphonics
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
I don't know if it's related to Big Sur or the M1, but on my new MacBook Pro (macOS 11.4), Max (8.1.11) crashes the moment the manta object is instantiated.
The text was updated successfully, but these errors were encountered: