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'm not sure if it's normal for it to be allocating metal twice, but I also see that elsewhere in the logs.
I believe this may be due to the metal allocation taking place after the app was sent to the background. The app seems to not crash if the transcription is already happening when backgrounded, but it does seem to crash if the backgrounding happens at around the same time as the metal library is being loaded.
Having a fallback or an error instead of an abort() would help to mitigate this. I'll do some more testing on my end to see when it's happening.
The text was updated successfully, but these errors were encountered:
Whisper 1.5.2 via Swift package
Whisper logs:
Stack trace:
I'm not sure if it's normal for it to be allocating metal twice, but I also see that elsewhere in the logs.
I believe this may be due to the metal allocation taking place after the app was sent to the background. The app seems to not crash if the transcription is already happening when backgrounded, but it does seem to crash if the backgrounding happens at around the same time as the metal library is being loaded.
Having a fallback or an error instead of an abort() would help to mitigate this. I'll do some more testing on my end to see when it's happening.
The text was updated successfully, but these errors were encountered: