Mir crashes from time to time when using Telegram while network changes [AndroidWindow: Caught exception at Mir/EGL driver boundary (in dequeueBuffer): Dynamic exception type: St11logic_error std::exception::what: state was not valid]
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Expired
|
Undecided
|
Unassigned | ||
| mir (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Hi,
for more than 2 months I've been occasionally experiencing Mir crashes when I use Telegram and my network connection changes from none to cellular and wifi - which happens a lot to me while travelling by subway and/or passing by shopping centers/
I've experienced this several times and it happened just after I sent a message via Telegram (the message actually got through, I could even see it being sent moments before my phone froze). It is however not unusual for me to experience this while I am composing a message either.
If this is not a pure Mir issue but something that Telegram causes so that Mir crashes I am pointing out that I only recall seeing this issue when Telegram is in the working state, that is not the broken one that ignores everything although network clearly works and incoming notifications appear and only way to fix this is to reopen the app.
Here is a Telegram log I have: http://
Thank you very much for looking into this. I am running rc-proposed on MX4.
| affects: | mir → unity8 |
| Gerry Boland (gerboland) wrote | #1 |
| zubozrout (zubozrout) wrote | #2 |
| zubozrout (zubozrout) wrote | #3 |
| Daniel van Vugt (vanvugt) wrote | #5 |
| summary: |
Mir crashes from time to time when using Telegram while network changes + [AndroidWindow: Caught exception at Mir/EGL driver boundary (in + dequeueBuffer): Dynamic exception type: St11logic_error + std::exception::what: state was not valid] |
| tags: | added: android |
| zubozrout (zubozrout) wrote | #6 |
| Daniel van Vugt (vanvugt) wrote | #7 |
| zubozrout (zubozrout) wrote | #8 |
| zubozrout (zubozrout) wrote | #9 |
| Daniel van Vugt (vanvugt) wrote | #10 |
| Daniel van Vugt (vanvugt) wrote | #11 |
| Changed in mir: | |
| status: | New → Incomplete |
| Changed in mir (Ubuntu): | |
| status: | New → Incomplete |
| tags: | removed: android |
| Launchpad Janitor (janitor) wrote | #12 |
| Changed in mir: | |
| status: | Incomplete → Expired |
| Launchpad Janitor (janitor) wrote | #13 |
| Changed in mir (Ubuntu): | |
| status: | Incomplete → Expired |
More likely it is something with unity8, but not impossible Mir is at fault. But without some kind of crash dump, and it being extremely hard to reproduce, this is hard to solve.
A crash dump was generated, and hopefully uploaded to our servers. You can see them by visiting System Settings, Privacy & Security, Diagnostics, Previous Error reports (opens webbrowser). Can you share any unity8 reports here?