mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #856] Application crashes when reconnecting MacBook with multi-output audio device #540
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#540
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bellwood on GitHub (Dec 22, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/856
Originally assigned to: @bellwood on GitHub.
Before opening the issue, have you...?
Describe the bug
I have a 2021 M1 MacBook Pro running Monterey 12.1.
I am driving (2) LG 32UL950-W via thunderbolt (chained)
I have each monitor and the MacBook Internal Speakers in a Multi-Output device using the Macs Audio Midi Setup.
At the end of each day, I unplug the primary screen from my MacBook and upon returning the next day, MonitorControl has crashed and I need to restart the application.
My co-worker has the same laptop and display setup and does not experience this crash, he however is not using multi-output for audio.
As a test, yesterday, I removed my multi-output before packing up and this morning MonitorControl was still running properly.
I am glad to provide additional testing or logging
Steps to reproduce
Create a multi-output audio device, add both displays and laptop speakers.
The application should crash upon disconnection of the displays or upon the displays being reconnected.
Expected behavior
The application should not crash
Anything else?
No response
Environment Information (please complete the following information)
@waydabber commented on GitHub (Dec 22, 2021):
Whoa, talk about an exotic use-case. :)
@waydabber commented on GitHub (Dec 22, 2021):
I was trying to recreate this problem by creating a multi-output device with the MacBook Speaker, display speaker (and also with a third USB audio device) and was trying to disconnect the display, but nothing seemed to happen. It is currently unclear why this happens. It would be useful to have a crash log or some console log outputs of MonitorControl.
Also - what are the volume control options set under Keyboard and do you have "Play feedback when volume is changed" enabled under Sound in System Preferences?
I am afraid the config is so exotic (new MB Pro and daisy chained thunderbolt displays) that it's going to be super difficult to reproduce this issue anywhere but with your config. The best thing you could do is download XCode, clone the project, run te app from XCode and try to recreate the problem. The XCode debugger should tell you exactly why and where did the app crash, this could give us more insight.
@bellwood commented on GitHub (Dec 22, 2021):
This is yesterday's crash log for the app:
Volume control: Standard keyboard volume and mute keys
Screen to control: Change volumes for all screens
OSD Scale: Checked
I do not
I am absolutely glad to figure out how todo this if the above crash report isn't helpful. I can provide a few others if needed.
Thank you!
@waydabber commented on GitHub (Dec 22, 2021):
To be honest, based on this changelog I have no idea what's wrong except that the app indeed crashed. :) But it seems that almost half an hour passed since last wake so it does not crash upon wake immediately.
I recommend you building and running the app in XCode and see why and how it crashes. For some audio operations MonitorControl uses a 3rd party package called SimplyCoreAudio, it is possible that the problem lies there - but in the crashlog I don't see any obvious inditcation that this is the case or that the problem is audio related at all.
If you do not use the aggregate device, the crash does not happen as well? If so, then what happens if you do not daisy chain the displays or connect each of the displays directly to the MBP?
@bellwood commented on GitHub (Dec 22, 2021):
Will do some testing and work to get you further details. Thanks =)
@waydabber commented on GitHub (Jan 2, 2022):
Hey Brian, let me know if you have any update on this as I still can't seem to reproduce the issue. Thank you!
@waydabber commented on GitHub (Jan 4, 2022):
Hi, I'll close this issue for now but we'll reopen it once we have more info and can progress with it. Thank you!
@bellwood commented on GitHub (Jan 4, 2022):
@waydabber thanks for assigning to me - I've a bit a travel here in the new year - will gladly follow up once I'm back in the office.