[Webkit-unassigned] [Bug 164052] [GTK] Since the memory pressure relief has been activated, my disk has a high usage and the desktop stalls

[bugzilla-daemon at webkit.org]

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

Carlos Garcia Campos <cgarcia at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cgarcia at igalia.com

--- Comment #3 from Carlos Garcia Campos <cgarcia at igalia.com> ---
(In reply to comment #2)
> (In reply to comment #1)
> > I think that it would be good, then, to have some public signal notifying
> > that WK is getting out of memory and the pressure relief is not helping.
> > 
> > That way, apps that are using WK will be able to warn the user about it.
> > 
> > For example, with Ephy, it could be displayed a warning in the fashion:
> > 
> > "Ephy is running out of memory. Please, close some tabs or other programs"
> 
> The same workload / number of tabs that used to work quite well without the
> memory pressure relief is now swapping. So I doubt WK is really running out
> of memory.
> 
> For what it is worth, I have 8GB of physical RAM.

That's a different issue though. This bug is about running the memory pressure handler several times when the memory situation is critical, assuming the measure is correct. Another issue is that we might be calculating the memory available wrongly, or that we are triggering the handler too early (we currently use 90%). Note also that the memory pressure doesn't monitors the webkit memory, but the system memory, so it's possible that it's not WebKit the one causing the high memory usage, but we try to help in any case by freeing caches, etc. In those cases it's common that we end up freeing very little memory or nothing, we could check that and increase the interval to install the handler again.
If you think we are measuring wrong, or that 90% is too early, file a new bug report, please.

-- 
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/20161028/f12a7303/attachment-0001.html>