Bug 235540 - Konqueror crawls (pegs CPU) when browsing long Blog with lots of video entries
Summary: Konqueror crawls (pegs CPU) when browsing long Blog with lots of video entries
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 4.3.5
Platform: Unlisted Binaries Linux
: NOR major
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-27 14:07 UTC by RGBl
Modified: 2022-11-13 05:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RGBl 2010-04-27 14:07:26 UTC
Application that crashed: konqueror
Version of the application: 4.3.5 (KDE 4.3.5) "release 0"
KDE Version: 4.3.5 (KDE 4.3.5) "release 0"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-0.2-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
I was browsing for a while when opened a link to a blog. After switching to the corresponding tab in which the blog was loading (the blog was really long, full of pictures and with youtube embedded objects) the Konqueror's performance dropped a lot, becoming sluggish. Then (before the blog was full loaded) I tried to close the tab: Konqueror did not respond and after a few seconds it crashed.

 -- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fbfdb477454 in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#6  0x00007fbfdb4837e5 in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#7  0x00007fbfe604ffbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#8  0x00007fbfdb42da4f in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#9  0x00007fbfdb42e613 in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#10 0x00007fbfdb483abd in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#11 0x00007fbfe604ffbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#12 0x00007fbfe6054fff in ?? () from /usr/lib64/libQtCore.so.4
#13 0x00007fbfe6049f63 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#14 0x00007fbfe3e232ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007fbfe3e2a57e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007fbfe4a1e016 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#17 0x00007fbfe603addc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x00007fbfe606671d in ?? () from /usr/lib64/libQtCore.so.4
#19 0x00007fbfe6063678 in ?? () from /usr/lib64/libQtCore.so.4
#20 0x00007fbfe2d6cdee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fbfe2d707b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fbfe2d708e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fbfe60633a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007fbfe3eb631e in ?? () from /usr/lib64/libQtGui.so.4
#25 0x00007fbfe6039712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007fbfe6039ae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007fbfe603bc99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#28 0x00007fbfdb4afcd3 in kdemain () from /usr/lib64/libkdeinit4_konqueror.so
#29 0x0000000000406f88 in _start ()

Reported using DrKonqi
Comment 1 RGBl 2010-04-27 14:18:35 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.
Comment 2 Dawit Alemayehu 2011-11-21 18:41:31 UTC
(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.
Comment 3 Raúl 2014-08-25 15:28:00 UTC
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.
Comment 4 Justin Zobel 2022-10-14 05:46:45 UTC
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!
Comment 5 Bug Janitor Service 2022-10-29 05:02:07 UTC
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!
Comment 6 Bug Janitor Service 2022-11-13 05:14:22 UTC
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!