[Webkit-unassigned] [Bug 126122] [GTK] Particular sites may hang entire desktop
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Feb 1 04:56:56 PST 2016
https://bugs.webkit.org/show_bug.cgi?id=126122
--- Comment #29 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
You can reproduce this without killing your desktop by using Linux's cgroups to limit the amount of memory that webkit can use. This way is easier to reproduce and test:
$ sudo cgcreate -g memory:/testwebkitmem
$ echo $(( 1 * 1024 * 1024 * 1024 ))| sudo tee /sys/fs/cgroup/memory/testwebkitmem/memory.limit_in_bytes
$ echo $(( 2 * 1024 * 1024 * 1024 ))| sudo tee /sys/fs/cgroup/memory/testwebkitmem/memory.memsw.limit_in_bytes
$ sudo cgexec -g memory:/testwebkitmem sudo -H -u $USER Tools/jhbuild/jhbuild-wrapper --gtk run ./WebKitBuild/Release/bin/MiniBrowser http://www.reuters.com/article/us-new-york-flightcenter-idUSKCN0SC14B20151018
So, I quickly get WebKitWebProcess killed by the kernel's OOM-killer:
Task in /testwebkitmem killed as a result of limit of /testwebkitmem
memory: usage 1048576kB, limit 1048576kB, failcnt 72526
memory+swap: usage 1967216kB, limit 2097152kB, failcnt 0
kmem: usage 0kB, limit 18014398509481983kB, failcnt 0
Memory cgroup stats for /testwebkitmem: cache:3480KB rss:1045096KB rss_huge:0KB mapped_file:3476KB writeback:285804KB swap:918640KB inactive_anon:524344KB active_anon:524192KB inactive_file:0KB active_file:0KB unevictable:0KB
[ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[17018] 0 17018 13843 806 31 120 0 sudo
[17019] 0 17019 13843 0 29 120 0 sudo
[17020] 1000 17020 515762 18778 226 6572 0 MiniBrowser
[17040] 1000 17040 775055 15724 312 6776 0 WebKitNetworkPr
[17042] 1000 17042 1085848 209041 1182 288385 0 WebKitWebProces
Memory cgroup out of memory: Kill process 17042 (WebKitWebProces) score 951 or sacrifice child
Killed process 17042 (WebKitWebProces) total-vm:4343392kB, anon-rss:752824kB, file-rss:83340kB
But, this doesn't kills or causes any instability on my system, so is a nice trick to debug memory problems.
My 2 cents.
--
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/20160201/3dd67619/attachment.html>
More information about the webkit-unassigned
mailing list