Re: Memory use in 2.22 with WebKitGTK 2.14
- From: Michael Catanzaro <mcatanzaro igalia com>
- To: Michael Gratton <mike vee net>
- Cc: "epiphany-list gnome org" <epiphany-list gnome org>
- Subject: Re: Memory use in 2.22 with WebKitGTK 2.14
- Date: Fri, 21 Oct 2016 20:09:00 -0500
On Sat, 2016-10-22 at 09:38 +1100, Michael Gratton wrote:
Re-running with compositing disabled does indeed reduce the memory
use
by a factor of almost 4: to 2GB total. Individual web processes are
now
being reported to use about ~1/5 of of the memory in g-s-m.
I wonder if my high-DPI display is causing the extra overhead when
it
is enabled compared to what you are seeing?
I got a response already (you are "he"):
"""If he can build WebKit, ask him to try also with a build with the
threaded compositor disabled (cmake arg
-DENABLE_THREADED_COMPOSITOR=OFF )
and without disabling AC mode via this env variable."""
Up for giving this a try? I know it takes a while to build. :( It will
help determine whether the problem is actually accelerated compositing
mode, or threaded compositor. (Threaded compositor is new in 2.14 and
requires accelerated compositing. Accelerated compositing has been
around for a while, but disabled except on a few web pages; in 2.14
it's now used everywhere.)
Michael
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]