[Webkit-unassigned] [Bug 164049] New: [GTK] Dramatic increase on memory usage since 2.14.x

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Oct 27 01:48:47 PDT 2016


https://bugs.webkit.org/show_bug.cgi?id=164049

            Bug ID: 164049
           Summary: [GTK] Dramatic increase on memory usage since 2.14.x
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: agomez at igalia.com
                CC: bugs-noreply at webkitgtk.org

This discussion started in ephy's ML by Michael Gratton, but opening a bug for reference:
https://mail.gnome.org/archives/epiphany-list/2016-October/msg00016.html

Hey all,

I feel like Epiphany's/WebKitGTK's memory use has substantially 
increased with 3.22/2.14, under X11 on Ubuntu at least.

My current Epiphany session has ~70 tabs over two windows. If I quit 
and restart it, such that only two of those tabs have actually loaded 
any content, then the total memory consumption is ~7GB (as reported by 
gnome-system-monitor total free before and after launching Ephy). This 
seems to be a substantial increase over earlier versions.

Breaking that down, I am seeing the following approx Memory (from 
g-s-m):
 - Epiphany: 100M
 - Network + DB processes: 40M
 - Single web process for loaded tabs: 250M (+ 10M XServer memory)
 - Single web process for not-yet-loaded tabs: 55M (+ 10M XServer 
memory)

While that doesn't add up to ~7GB, adding up the RSS sizes as reported 
by `ps aux` does.

Switching to a single-shared-process gives 6.4G used after launch, with 
similar numbers for the aux processes, and the following for the single 
web process:

 - Shared web process: 2.1G (+ 550Mb XServer memory)

This is in comparison to the honourable competition, both of which use 
~1G after opening 70 blank tabs.

Is this to be expected? What's the best way to try to find out where 
all this memory is going?

//Mike

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161027/349a1e5d/attachment.html>


More information about the webkit-unassigned mailing list