-
Was this a one time issue? or after the restart of the app, it happened again?
This stack trace does not give me much and from what I can see there as a race-condition/deadlock between drawing code in BeagleIM (possible WebRTC) and macOS WindowServer. Why BeagleIM was waiting for WindowServer (and even GeForce driver was mentioned) I cannot tell.
Was this issue between two macOS devices? Which one was initiating device?
-
@kobit Have you restarted BeagleIM since the issue happened? (initial failure) If not, could you attach logs from BeagleIM?
-
Shortest log is from file attempt.
Type |
Bug
|
Priority |
Normal
|
Assignee |
Issue Votes (0)
Watchers (0)
I tried to make video call to Artur. When I pressed camera button, Beagle immediately frozen: beach ball was spinning. When I killed application, crash report dialog was open: