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

Crash in NSStatusBarButton updateConstraints #11619

Closed
cyberduck opened this issue Mar 19, 2021 · 2 comments
Closed

Crash in NSStatusBarButton updateConstraints #11619

cyberduck opened this issue Mar 19, 2021 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 19, 2021

f09e04e created the issue

I use onedrive sharepoint cloud storage, uploading ~200Mb files while the app crashes.
Console log attached.
The issue in the log:

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
Crashing on exception: The layout constraints still need update after calling -[NSStatusBarButton updateConstraints].  NSStatusBarButton or one of its superclasses may have overridden -updateConstraints without calling super. Or, something may have dirtied layout constraints in the middle of updating them.  Both are programming errors.
abort() called

Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 19, 2021

@dkocher commented

Thanks for the bug report. Is this crash reproducible?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 9, 2021

@dkocher commented

Please write to [mailto:support@mountainduck.io] if you can still reproduce.

@cyberduck cyberduck closed this Apr 9, 2021
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant