Mir

Mir leaves apps in unusable state

Bug #1645808 reported by Brandon Schaefer
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mir
Expired
Critical
Unassigned
0.25
Expired
Critical
Unassigned

Bug Description

From QA testing:

http://paste.ubuntu.com/23554278/

Resulting in apps unable to launch.

Test on silo 2180
ppa:ci-train-ppa-service/2180

Revision history for this message
Kevin DuBois (kdub) wrote :

I'm trying to reproduce on m10 as the QA team did (although it doesn't look m10-specific).

Changed in mir:
milestone: none → 0.26.0
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Brandon Schaefer (brandontschaefer)
Revision history for this message
Brandon Schaefer (brandontschaefer) wrote :

Log files that may be helpful

Kevin DuBois (kdub)
Changed in mir:
milestone: 0.26.0 → 0.25.0
Revision history for this message
Kevin DuBois (kdub) wrote :

was able to reproduce, seems like OOM killing the client, probably a leak.

Revision history for this message
Kevin DuBois (kdub) wrote :

easier way to reproduce is to rotate the device 40 or so times

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Hmm, the only thing big enough to kill Mir that quickly is probably buffers/display buffers. Perhaps related to r3712?

Changed in mir:
milestone: 0.25.0 → 0.26.0
status: Triaged → New
status: New → Confirmed
Revision history for this message
Brandon Schaefer (brandontschaefer) wrote :

It was also reproduced on 0.24.1. So not 0.25 directly.

Revision history for this message
Kevin DuBois (kdub) wrote :

Right, I could reproduce with the stock image for freiza_arm64 (mir 0.24.1), as well as with mir 0.25.0. I could also see the issue with frieza (armhf) with mir 0.24.1.

Revision history for this message
Kevin DuBois (kdub) wrote :

I could also see this on mx4 with the X+O channel, so it doesn't look 64 bit-specific, or device-specific.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

How sure are you this is a Mir bug at all? Can anyone reproduce it just using mir-demos?

Changed in mir:
status: Confirmed → Incomplete
Revision history for this message
Brandon Schaefer (brandontschaefer) wrote :

Yeah something we need to look into.

summary: - Mir 0.25 leaves apps in unusable state
+ Mir leaves apps in unusable state
Changed in mir:
milestone: 0.26.0 → none
assignee: Brandon Schaefer (brandontschaefer) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mir because there has been no activity for 60 days.]

Changed in mir:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mir 0.25 because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.