After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 578849 - valgrind run against epiphany-browser shows large memory losses
valgrind run against epiphany-browser shows large memory losses
Status: RESOLVED WONTFIX
Product: epiphany
Classification: Core
Component: [obsolete] Backend:Mozilla
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-04-13 16:49 UTC by C de-Avillez
Modified: 2009-08-04 07:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
valgrind log (101.01 KB, application/x-compressed-tar)
2009-04-13 16:51 UTC, C de-Avillez 		Details

Description C de-Avillez 2009-04-13 16:49:13 UTC 
original Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/217602

I ran valgrind against Epiphany; just opened the browser on an empty page, and closed it.

hggdh@xango2:~ $ apt-cache policy epiphany-browser
epiphany-browser:
  Installed: 2.26.0-0ubuntu3
  Candidate: 2.26.0-0ubuntu3
  Version table:
 *** 2.26.0-0ubuntu3 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status
hggdh@xango2:~ $
Comment 1 C de-Avillez 2009-04-13 16:51:11 UTC 
Created attachment 132601 [details]
valgrind log
Comment 2 Christian Persch 2009-04-13 17:14:55 UTC 
I'm sorry, but the gecko backend is not actively maintained anymore and thus won't see any leak fixes. Also, enabling python extensions isn't useful when searching for leaks. Also I don't see "large" memory losses; the *definitely lost* memory is quite small.
Comment 3 C de-Avillez 2009-04-13 18:43:24 UTC 
thanks, Christian. I guess we can close this one, then, as won't fix.
Comment 4 Priit Laes (IRC: plaes) 2009-08-04 07:47:22 UTC 
Closing per Chpe's answer.