149037 2015-09-10 09:42:01 -0700 [GTK] WebKitWebProcess WebKitGtk+ uses memory without end when visiting some LinkedIn URL 2016-01-29 06:23:21 -0800 1 1 1 Unclassified WebKit WebKitGTK WebKit Local Build Unspecified Unspecified RESOLVED DUPLICATE 126122 P2 Normal --- 1 agomez webkit-unassigned mcatanzaro oldest_to_newest 1124914 0 agomez 2015-09-10 09:42:01 -0700 I'm using WebKitGtk+ with my own JHBuild setting: https://github.com/tanty/jhbuild-epiphany/tree/wkgtk-devel MiniBrowser against WebKit 2.8.5 I log in into my LinkedIn profile. Then, from the top bar I place my pointer over the "Connections" menu so it is expanded, once expanded, I click on the "See all" link: https://www.linkedin.com/people/pymk/hub?ref=global-nav&trk=nav_utilities_invites_header Upon doing so, the browser freezes and I notice the HD of my computer starting to work hard. After checking with "top" the WebKitWebProcess is growing its used memory by the Gbs!!! and it doesn't seem to stop. This may not be a problem in WKGTK+ but the graphics driver since, after repeating the process with a GDB attached to the WebKitWebProcess, GDB states that the point in which it exits when manually killing the process is: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so However, I cannot reproduce with Chromium, FF (of course, the code path is completely different). 1124918 1 agomez 2015-09-10 09:54:04 -0700 Reproducible also with my distro's Epiphany 3.12.1 and WebKitGTK+ 2.4.8. 1124923 2 agomez 2015-09-10 10:04:21 -0700 Feel free to close if you think this is just Mesa related: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1494402 1160099 3 agomez 2016-01-29 06:19:29 -0800 Still reproducible with 2.10.6 1160101 4 mcatanzaro 2016-01-29 06:23:21 -0800 (In reply to comment #0) > This may not be a problem in WKGTK+ but the graphics driver since, after > repeating the process with a GDB attached to the WebKitWebProcess, GDB > states that the point in which it exits when manually killing the process is: > /usr/lib/x86_64-linux-gnu/dri/i965_dri.so It's a WebKit problem. Different graphics drivers just fail differently, e.g. [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to parse relocation -12 *** This bug has been marked as a duplicate of bug 126122 ***