| Summary: | Konqueror crawls (pegs CPU) when browsing long Blog with lots of video entries | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | RGBl <rgbl> |
| Component: | khtml | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | niss24079, rasasi78 |
| Priority: | NOR | ||
| Version First Reported In: | 4.3.5 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
RGBl
2010-04-27 14:07:26 UTC
I tried to open the blog again. This time konqueror did not crash, but it become sluggish and the system resources usage exploded: the cpu arrived at 90ºC before I was able to close the tab. The blog is this one: http://elshowdecarlitosbala.blogspot.com/ Konqueror started to download small txt files to some tmp folder on the .kde4 folder. (In reply to comment #1) > I tried to open the blog again. This time konqueror did not crash, but it > become sluggish and the system resources usage exploded: the cpu arrived at > 90ºC before I was able to close the tab. > The blog is this one: > http://elshowdecarlitosbala.blogspot.com/ > Konqueror started to download small txt files to some tmp folder on the .kde4 > folder. Cannot reproduce the crash and the backtrace is useless since you did not have the debug version of the proper packages installed. I also cannot reproduce the slagishness when using the webkit browser engine. However, I definitely see it with with khtml ; so I am reassigning this to the proper module. What I see here (kdelibs 4.14.0 + konqueror 4.13.3) is that konqueror keeps being responsive in the first seconds (maybe first minute) of that web loading. After that, when page is 80% loaded it starts eating memory and konqueror starts being unresponsive. I loaded that web on a separate konqueror instance, in the only tab. It took about 1.3GB RSS. This is a system information memory report: Summary The process konqueror (with pid 15109) is using approximately 1.2 GB of memory. It is using 1.2 GB privately, and a further 19.8 MB that is, or could be, shared with other programs. Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 5.8 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 1.2 GB. Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings, plus the stack of its 2 threads. Private 1293468 KB [heap] 976 KB /usr/lib/libkhtml.so.5.14.0 388 KB /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.6 312 KB /usr/lib/libkdeui.so.5.14.0 212 KB /usr/lib/libkio.so.5.14.0 Shared 4192 KB /SYSV00000000 (deleted) 3092 KB /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.6 2144 KB /usr/lib/libkhtml.so.5.14.0 1316 KB /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.6 1308 KB /usr/lib/libkdeui.so.5.14.0 So it's about 1.3GB heap it consumes. Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported and confirmed, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |