-
-
Notifications
You must be signed in to change notification settings - Fork 335
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
Bug: eqMac crashed due to: "NSWindow drag regions should only be invalidated on the Main Thread!" #222
Comments
Roman, I'm very sorry I caused unnecessary work. Sorry again! |
Well I think someone else reported this as well somewhere 😅 I will see if anyone else leaves any feedback and if not I will close this |
I will close this issue. Please comment on this issue if this error reoccurs. Thanks |
Still an issue with eqMac 0.1.0 beta on macOS 10.14.6. |
Reported again in #256 |
Still crashes everytime on startup with 0.1.1 Process: eqMac [1073] Date/Time: 2020-05-01 08:56:48.014 -0400 Time Awake Since Boot: 1200 seconds System Integrity Protection: enabled Crashed Thread: 2 Dispatch queue: check-driver-shown Exception Type: EXC_CRASH (SIGABRT) Application Specific Information: Application Specific Backtrace 1: |
For me too |
Same here with 0.1.1 on Catalina 10.15.4 |
Just release v0.2.0 please check if the issue still persists. |
v0.2.0 did start correctly for me, instead of immediately crashing, so that's progress. Let's await some hours of testing before concluding that this is fixed. |
I'm closing this issue for now as it's seems it's fine now as of v0.2 If that is not the case please tell me and I will reopen the issue |
Reopening as people have reported this problem still persisting even in v0.2.0 |
Sorry, my bad, I didn't know that I could reply to closed bugs. Very new to Github. |
Well, I just got 10.15.5 and it works again. Sorry for bringing this up. |
eqMac 0.2 was working fine for me until today, where it won't run. Starts up, I see the menu bar icon for a couple seconds, then it goes away. Here's what seems relevant from the crash log:
|
I've also deleted everything in ~/Library with eqMac in the name and can't get it to come back to life. It also seems like maybe it's remembering stuff some other way, because it seems to still be starting up in menubar-only mode, which isn't the default, IIRC. |
Yep, eqMac has microphone perms enabled on my system. BUT, if I disable it and then start eqMac, I get the "allow microphone permission?" dialog. I click "proceed" and eqMac crashes immediately. If I then approve it again and re-start eqmac, it loads and doesn't exit! So, I think you're on to something there, even though it's more complicated than just not being permitted (according to the check box). I'm on Mojave, by the way. |
I realised the underlying cause of why it's happening, but I'm not sure where is it happening from, if that makes sense. I will try to mitigate the underlying issue and also release a new version with Debug Symbols included, so the crash logs have more information I can use. |
Cool, well, at least I have a workaround, so very much appreciate that. I'll be glad to run the version with symbols and re-report if I can reproduce it again. |
Can you please download pre-release version v0.2.1 from here: |
I get "unable to activate audio driver" when I start that version. I "try again" just causes it to exit. What am I doing wrong? |
I was having this issue on previous versions as well, and also as @kk7ds is saying v.0.2.1 shows 'Driver failed to activate' when starting up. |
That should be reported as a separate issue for this version. Possibly equal to #291, although that issue doesn't specify the app version. Report there. |
This issue should be resolved in v0.3.1. |
Disclaimer:
Please go through existing issues to avoid creating duplicates. If you found a similar issue please post a comment there. If you are uncertain your issue is related to others then create the issue. Obvious ignorance of this rule might get you blocked from posting new issues. Please tick the box below to show that you have followed the guideline.
Describe the bug
Reported in #216
eqMac crashed due to error:
Steps to Reproduce
Could not reproduce my end. Waiting for users to report on what they did to cause such error to occur
Setup information:
Waiting for users to report the fields below
Screenshots or Console.app logs
Full crash dump from issue #216
Additional information
Waiting for a chance to see the error happen to myself, also waiting for more info from users.
The text was updated successfully, but these errors were encountered: