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 766158 - Massive memory leak on certain sites
Massive memory leak on certain sites
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: General
3.20.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-05-09 08:09 UTC by Alexey Galakhov
Modified: 2016-05-09 13:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexey Galakhov 2016-05-09 08:09:45 UTC
On certain sites, epiphany keeps eating virtual memory until the OOM killer is activated. This includes livejournal.com and possibly even some parts of linkedin.com.

How to reproduce:
- enter livejournal.com (I switched the site to old design, if it matters)
- keep scrolling down
- watch memory consumption

This does not reproduce in other browsers using webkit2gtk on the same machine.

My installation of Epiphany comes from Arch Linux. No additional plugins/userscripts are installed.
Comment 1 Michael Catanzaro 2016-05-09 13:26:27 UTC
(In reply to Alexey Galakhov from comment #0)
> This does not reproduce in other browsers using webkit2gtk on the same
> machine.

That seems unlikely; what other browsers are you testing?

I'm pretty sure this is WebKit #126122. Rest assured this is a very high priority issue for us at the moment.
Comment 2 Michael Catanzaro 2016-05-09 13:29:50 UTC
(In reply to Michael Catanzaro from comment #1)
> That seems unlikely; what other browsers are you testing?

Actually, come to think of it, I can't think of any browser besides Epiphany that uses webkit2gtk... are you sure it's using webkit2gtk?
Comment 3 Alexey Galakhov 2016-05-09 13:38:33 UTC
Yes, I'm sure. The same site works fine in i.e. lariza. I carefully choosed webkit2gtk browsers only.

$ ldd /usr/bin/lariza
...
libwebkit2gtk-4.0.so.37 => /usr/lib/libwebkit2gtk-4.0.so.37 (0x00007f8449aa4000)
...

$ ldd /usr/bin/epiphany
...
libwebkit2gtk-4.0.so.37 => /usr/lib/libwebkit2gtk-4.0.so.37 (0x00007f4cf11d7000)
...

Looks like epiphany has at least something that triggers the WebKit issue.