Comment 4 for bug 522384
Revision history for this message
| Alexandr Grigorcea (cahr-gr) wrote Re: [Bug 522384] Re: Memory leak | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
ok. I've found where iPdf pages are destroyed, but what happens with
temporary pixbufs? they are still there, shouldn't you unref them?
from library.gnome:
Creates a new GtkImage<http://
*pixbuf*. The GtkImage<http://
not assume a reference to the pixbuf; you still need to unref it if
you
own references.
GtkImage<http://
add its own reference rather than adopting yours.
and, as I unterstand, you should call g_object_
~iPdf(). otherwise m_document remains in memory
On Wed, Feb 17, 2010 at 2:42 PM, Jordi Puigdellívol <email address hidden>wrote:
> It seems that I lose mem in the scale_pixbuf function..
> And in other sites, I use valgrind to check this but I couldn't find the
> source..
>
> iPdf has a destroy method that unrefs all pages, I think is called
>
> In gloobus-
> called everytime you change file or you quit gloobus-preview.
> It calls the end function and the destructors as it destroys the plugin.
>
> the iDocument::destroy does nothing cause its done by the iPdf plugin,
> if you run with --debug i think you'll see the destroyng page messages..
>
> but sure there are more memleaks
>
> I'll merge with your patch and try to track more of them today
>
> Thanks!
>
> --
> Memory leak
> https:/
> You received this bug notification because you are a member of Gloobus
> Developers, which is the registrant for gloobus-preview.
>
> Status in Gloobus Preview: Confirmed
>
> Bug description:
> I've already reported this here
> https:/
> files , but now I noticed that it happens with any kind of files
> opened a folder with 2 images, after 20-30 switches got 24% of memory usage
> of my 4Gb
> some files eat less memory, other more
> rev173
>
>
>