RESOLVED FIXED 186663
[GTK][WKE] Disable memory pressure handling when running layout tests (WTR)
https://bugs.webkit.org/show_bug.cgi?id=186663
Summary [GTK][WKE] Disable memory pressure handling when running layout tests (WTR)
Carlos Alberto Lopez Perez
Reported 2018-06-15 09:16:59 PDT
It seems a good amount of flakiness in the GTK and WPE layout tests is caused by the in-webprocess memory pressure monitor. You can see that in the following logs: https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r232868%20(7018)/results.html <-- the crash is our memory pressure killer https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r232867%20(7017)/results.html <-- second crash is our memory pressure killer https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r232866%20(7016)/results.html <-- the crash is our memory pressure killer https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r232864%20(7015)/results.html <-- first crash If it helped us find tests using too much memory, it might be useful, but it does not because the test that dies is probably just running in a process that previously leaked a bunch of memory... i.e. the test that is killed is probably not the test that has a real problem. The ideal solution would be to fix the cause of those leaks that accumulate over the course of those runs. But meanwhile we don't have that right fix a workaround that we can do now to avoid flakiness in our tests is to disable this memory pressure monitor when running with WTR.
Attachments
Patch (4.93 KB, patch)
2018-06-15 10:01 PDT, Carlos Alberto Lopez Perez
mcatanzaro: review+
Carlos Alberto Lopez Perez
Comment 1 2018-06-15 10:01:33 PDT
Michael Catanzaro
Comment 2 2018-06-15 10:05:08 PDT
Comment on attachment 342820 [details] Patch Thanks. I had been complaining about this all year. This is really only harmful when running layout tests.
Carlos Alberto Lopez Perez
Comment 3 2018-06-15 10:35:39 PDT
Note You need to log in before you can comment on or make changes to this bug.