Bartosz Małkowski opened 5 years ago
|
|
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? |
|
I tried to start call. I didn't tried to reproduce this problem, because Artur called to me from Siskin and we established video call (btw: he cannot do that from Beagle). |
|
Artur is not able to call from Beagle? or it is not possible to establish a video call? |
|
We did this:
|
|
Then, the question is: "Where are logs from the failed attempt?". It is possible that something was not deinitialized properly and caused a crash. |
|
@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. |
|
Due to changes in the used "ICE servers" list, this issue is solved already. |
Type |
Bug
|
Priority |
Normal
|
Assignee |
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: