Bug 247943
Summary: | nautilus leaks memory when changing backgrounds due to leak of GnomeBG's file_cache | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Baron <dbaron> | ||||
Component: | gnome-desktop | Assignee: | Ray Strode [halfline] <rstrode> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 7 | CC: | sandmann, sereinity, ymedhui | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-08-31 19:15:47 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
David Baron
2007-07-12 07:45:30 UTC
Created attachment 159037 [details]
stack showing where the leaked memory is allocated
This is the stack at which the leaked memory is allocated. (Well, actually, a
function call whose first parameter is the memory right after it's allocated,
which is a good point to break in gdb to see the address.)
I'd also note that a second reference to the same pixbuf is owned by the
pixbuf_cache member of the GnomeBG. This means that when clear_cache is
called, the g_object_unref lowers the reference count from 2 to 1; I'm
asserting that the other reference is owned by the file_cache member of the
same background.
The following two reports seem to describe a similar problem. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245660 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249283 *** Bug 249283 has been marked as a duplicate of this bug. *** *** Bug 245660 has been marked as a duplicate of this bug. *** |