Re: Memory use in 2.22 with WebKitGTK 2.14



On Fri, Oct 21, 2016 at 10:40 PM, Michael Catanzaro <mcatanzaro igalia com> wrote:
That's about twice what I'm seeing here, but I think the memory
increase is indeed expected in 2.14 due to the switch to always-on
accelerated compositing. You can verify by re-rerunning your experiment
with WEBKIT_DISABLE_COMPOSITING_MODE=1.

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?

The WebKitGTK+ mailing list would be a better place for this
discussion; there might already be plans to improve this.

Sure looks like it, I'll take it over there.

Cheers,
//Mike

--
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]