<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Since the memory pressure relief has been activated, my disk has a high usage and the desktop stalls"
href="https://bugs.webkit.org/show_bug.cgi?id=164052#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Since the memory pressure relief has been activated, my disk has a high usage and the desktop stalls"
href="https://bugs.webkit.org/show_bug.cgi?id=164052">bug 164052</a>
from <span class="vcard"><a class="email" href="mailto:rishi.is@lostca.se" title="Debarshi Ray <rishi.is@lostca.se>"> <span class="fn">Debarshi Ray</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=164052#c3">comment #3</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=164052#c2">comment #2</a>)
>> 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.
>
> 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.</span >
I can reliably make it swap with just one terminal (running screen over SSH) and epiphany with a dozen tabs. The tabs have a bunch of bugzilla.gnome.org pages, and some other websites. The tabs act as a TODO list, so I have had them for a while and it wasn't a problem before.
It can always be some other thing that is eating away memory. However, it seems unlikely since this happens just after opening some new tabs on a freshly booted machine.
<span class="quote">> If you think we are measuring wrong, or that 90% is too early, file a new
> bug report, please.</span >
Or I can wait for this bug to be fixed and see if it also addresses my problem. :)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>