** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** No longer affects: qtmir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause
This bug was fixed in the package qtmir -
0.4.6+15.10.20150930.1-0ubuntu1
---
qtmir (0.4.6+15.10.20150930.1-0ubuntu1) wily; urgency=medium
[ CI Train Bot ]
* New rebuild forced.
[ Daniel d'Andrada ]
* MirSurfaceItem: texture must be manipulated only from the scene
graph
** Changed in: qtmir
Status: In Progress => Fix Released
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:ubuntu/wily-proposed/qtmir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive ui but power button
works display
To
*imagining*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive ui but power button
works display
To manage notifications about this bug
aacid:
Can you please test the attached proposed branches? I'm wondering if I'm
imaging things when it seems fixed.
** Branch linked: lp:~dandrader/qtmir/textureCleanUp-lp1499388
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that the fd leaking on killing apps like explained in
comment #18 also seems to stop for me when using
https://code.launchpad.net/~dandrader/qtmir/textureCleanUp-
lp1499388/+merge/272452
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Awesomtastic
** Changed in: qtmir
Assignee: Daniel van Vugt (vanvugt) => Daniel d'Andrada (dandrader)
** Changed in: qtmir
Assignee: Daniel d'Andrada (dandrader) => Daniel van Vugt (vanvugt)
** Changed in: qtmir
Assignee: Daniel van Vugt (vanvugt) => Daniel d'Andrada (dandrader)
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Status: New => Triaged
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Handy tip:
You can see the call stack of (many but not all) fds unity8 has open while it's
running. Just start unity8 under valgrind with --track-fds=yes. Then you can
get the live list of fds with their backtraces:
vgdb v.info open_fds
Annoyingly this doesn't show the dmabuf ones we're
Just noting, i agree with drop in priority, since we have a fix for u-a-l and
that was the original culprit.
we do need to eventually get this nailed, so please keep this as a front burner
activity
** Changed in: canonical-devices-system-image
Importance: Critical => High
--
You received
** Branch linked: lp:~vanvugt/qtmir/fix-1495871
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive ui but power button
works display
To
Dropped severity because the bug requires significant time to occur, if
at all.
** Changed in: qtmir
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
** Package changed: qtmir (Ubuntu) => qtmir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file
Note that tools like valgrind (memcheck) are unlikely to find the
problem. Because C++ and RAII... the offending resources get released on
shutdown and never actually leaked. So instead of leaks, you have to
hunt for "bloat" and use a memory/resource profiler.
I got distracted for a long time
Mir does associate resources with a client socket that are not released
until one of two things happen:
1. The client explicitly disconnects
2. An operation (like the outstanding read attempt) on the socket reports an
error
AFAIK there is no *guarantee* that the latter happens in a timely
Considering bug 1498816, and the new-ish bufferstream logic in Mir's
SessionMediator, I'm suspicious that Mir might just be indefinitely
bloated, never releasing some resources until shutdown. It's a bit scary
that the bufferstream logic is passing around raw pointers without any
clear ownership.
Actually there might still be a qtmir-specific leak but we need to fix
the leaks seen in plain Mir too --> bug 1498361
** Changed in: qtmir (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Using comment #18 on arale, I find roughly three fds are leaked at a
time:
> lrwx-- 1 phablet phablet 64 Sep 22 07:49 135 -> anon_inode:dmabuf
> lrwx-- 1 phablet phablet 64 Sep 22 07:49 138 -> /dev/pvrsrvkm
> lrwx-- 1 phablet phablet 64 Sep 22 07:49 139 -> /dev/pvrsrvkm
--
You
Apparently we fixed a very similar bug on desktop two years ago --> bug
1185183
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive ui but
Invalid for qtmir, but it does seem to be a Mir issue... See bug
1498361.
** Changed in: qtmir (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
Adding qtmir since i can make the anon_inode:dmabuf fd not leak by
making qtmir not free early the session when the app is killed.
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubuntu-app-launch (Ubuntu)
Status: In Progress => Fix Released
** Changed in: qtmir (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FWIW the ubuntu-app-launch fix has landed in the vivid image
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive ui but power button
unfortunately gerry's probably the best expert but out, assigning to
daniel in hopes he can make some progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've found two ways (which are effectively the same) to workaround the fd leak
caused by killing an app (comment #18)
* removing surfaceItem.surface = null; in unity8 SurfaceContainer.qml
* removing the 3 deleteLater in qtmir session.cpp
Both have the same effect. qtmir's session and
The anon_inode:dmabuf i mention in #18 is not leaked anymore if we make
ApplicationScreenshotProvider::requestImage return an empty QImage and
is still leaked if we return a QImage with junk data (without calling
mir::screenshot) so it seems it's not mir.
I'm investigating now if it's either
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive
If it's useful to anyone, here is a small script to track the number of
fd used per process. By default t takes a sample every 5 minutes. Then
you can diff the logs to find which process is suspicious.
** Attachment added: "topfd.sh"
The leaks in unity8 when the memory pressure is high can be easily reproduced
by:
* Be on dash
* Open an app
* Switch to he dash
* Use kill -9 to fill the app
We're leaking an anon_inode:dmabuf fd each time that happens.
--
You received this bug notification because you are a member of
removing media-hub, spawing bug 1496894
** No longer affects: media-hub (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive ui
> Have we confirmed that all the leaks in these scenarios can be traced back to
> this u-a-l leak?
No we have not, it'll be easier once this one has been fixed, but given we
don't use eventfd nor glib extensibly, there's a high chnange this is not in
unity8 itself
> If not, we need to ensure
>> If not, we need to ensure this is reflected in the bug status (by keeping
>> unity8 as affected), or opening a new bug report.
> I guess this is a matter of taste, feel free to re-add it if you prefer.
I just want to make sure we track this properly, not close it when the
u-a-l part is fixed
I can confirm that Ted's branch seems to fix all the fd leaking for me.
A second source would be cool.
It's a bit unfortunate we need ~8 fd per app though, may we need to
optimize that at some point in the future.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
s/second source/second confirmation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive ui but power button
works display
To manage
On Wed, 2015-09-16 at 15:22 +, Albert Astals Cid wrote:
> It's a bit unfortunate we need ~8 fd per app though, may we need to
> optimize that at some point in the future.
It will go down a bunch with the switch to systemd as we can request on
the system bus instead of building a custom dbus
using ted's branch
https://code.launchpad.net/~ted/ubuntu-app-launch/lp1495871-unref-context-15.04/+merge/271373
which is conveniently available in silo 60
i tested using the script above to open/close apps...which kept the number of
open fd's to a steady state
however, i then modified the
just out of curiosity, i set up the phone sim, sent text messages - since
that's when this seems to happen the most
the fds for unity8 would jump up by 1 but eventually drop back down by one.
I also watched the fd count for message+ & indicator-message-service which
stayed constant with sending
ok, watched pulseaudio and mediahub-server using the phonesim
pulseaudio was fine
media-hub-server was leaking fds, leaking 2 per text message alert & phone call
** Also affects: media-hub (Ubuntu)
Importance: Undecided
Status: New
** Changed in: media-hub (Ubuntu)
Importance:
** Changed in: ubuntu-app-launch (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive ui
had a question earlier today also if this was on stable (ota6) i just
confirmed it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
unity8 leaks file descriptors cause unresponsive
** Summary changed:
- unity8 leaks file descriptors
+ unity8 leaks file descriptors cause unresponsive ui but power button works
display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495871
Title:
43 matches
Mail list logo
