|Summary:||frame inside frame recursion at blog of SAP manager makes Konqueror use insane amounts of memory and cpu time|
|Product:||konqueror||Reporter:||Martin Steigerwald <Martin>|
|Component:||khtml||Assignee:||Konqueror Developers <konq-bugs>|
|Latest Commit:||Version Fixed In:|
Description Martin Steigerwald 2005-11-15 10:41:36 UTC
Version: (using KDE KDE 3.4.2) Installed from: Debian testing/unstable Packages OS: Linux Hello, although Shai Agassi says "I Love opensouce - really!" at least his blog bombs out Konqueror badly: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1700 as mentioned in: http://www.heise.de/newsticker/meldung/66168 Its a frame opening inside a frame opening inside a frame kind of bug that makes Konqueror eat gradually increasing amount of memory and cpu time up to a point where I had to use Ctrl-Alt-Esc on the Konqueror window to stop that denial of service attack: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 16098 martin 18 0 919m 226m 8608 R 0.7 60.2 13:27.33 konqueror I stopped it before memory got exhausted completely: martin@deepdance:~ -> free total used free shared buffers cached Mem: 385452 380472 4980 0 308 22752 -/+ buffers/cache: 357412 28040 Swap: 979924 856176 123748 Step to reproduce: - point konqueror to this URL: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1700 In early stage the frame inside frame recursion can be stopped by pressing the button to stop the transfer. Konqueror should limit the amount of frames inside frames to a sensible amount to avoid this kind of denial of service attack - not many more that are visible on a 21 inch TFT display or so I think. Well I wouldn't be surprised if you have such taken such a precaution already, but it doesn't seem to work here. Mozilla Firefox 1.07 as well as Opera 8.5 however do not show the frame inside frame inside frame behavior and just show one frame. Regards, Martin Steigerwald
Comment 1 Martin Steigerwald 2005-11-15 10:45:27 UTC
For the figure about memory consumption: I opened this blog another time to see if that behavior is reproducable. Before I did this it seemed, that the frame inside frame recursion had come to an end, Konqueror did not eat more memory - so it may well be that an internal frame inside frame limit in Konqueror has already been reached. Still I consider the amount of resources just for one opening of the blog already quite insane and as Mozilla Firefox and Opera do not show that behavior, there might well be a fixable bug hidden in Konqueror.
Comment 2 Philip Rodrigues 2006-09-07 21:53:22 UTC
At least the konqueror rendering is wrong (well, different to FF at least) - firefox doesn't open frames within frames on that page, while konqueror does. I didn't leave it long enough to see if it got to OOM.
Comment 3 Tommi Tervo 2006-12-19 15:49:56 UTC
*** Bug 139011 has been marked as a duplicate of this bug. ***
Comment 4 Gregor B. Rosenauer 2007-04-27 19:30:21 UTC
same problem here, try this one on the same site: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2824 Konqueror renders frame after frame, nesting each one in the other, making the result an interesting work of art but resulting in a totally weird and unreadable UI clutter...,-) Opens fine in Firefox 220.127.116.11.
Comment 5 Frank Reininghaus 2008-04-20 01:30:14 UTC
Comment 6 Maksim Orlovich 2008-04-20 03:19:14 UTC
Wow, thanks for the phenomenal analysis. I am collecting a whole bunch of issues in this area ATM, and this is an angle I didn't think of... Thankfully testing the last bullet is much easier with a source build..
Comment 7 Martin Steigerwald 2012-03-06 08:10:14 UTC
I am closing this, cause I can´t reproduce this with Konqueror from KDE SC 4.7.4 anymore, neither with webkit nor khtml. The page I mentioned just displays fine. Since I don´t see a fix targeted at this in the comments, I am closing this as "WORKSFORME". Feel free to reopen when there is still an issue left or adapt resolution to something else as you see fit. (First comment of mine with new Bugzilla;)