Bug 241699

Summary: Crash browsing some blogs and gmail
Product: [Applications] konqueror Reporter: RGBl <rgbl>
Component: generalAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: investigated, triaged
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description RGBl 2010-06-14 06:11:54 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 had some blogs opened together with my gmail account. Changing tab to one of those blogs I tried to scroll with the mouse wheel. The scroll bar moved but not the page. Konqueror started to grab system resources and the cpu temperature started to grow. I tried to close the tab and then konqueror crashed.

 -- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f8a03c20953 in __dynamic_cast () from /usr/lib64/libstdc++.so.6
#6  0x00007f89fb65cebe in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#7  0x00007f89fb6697e5 in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#8  0x00007f8a06235fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#9  0x00007f89fb613a4f in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#10 0x00007f89fb614613 in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#11 0x00007f89fb669abd in KConfigGroup::writeEntry(QString const&, QStringList const&, QFlags<KConfigBase::WriteConfigFlag>) () from /usr/lib64/libkdeinit4_konqueror.so
#12 0x00007f8a06235fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x00007f8a0623afff in ?? () from /usr/lib64/libQtCore.so.4
#14 0x00007f8a0622ff63 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#15 0x00007f8a040092ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f8a0401057e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f8a04c04016 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#18 0x00007f8a06220ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007f8a0624c71d in ?? () from /usr/lib64/libQtCore.so.4
#20 0x00007f8a06249678 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007f8a02f52dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f8a02f567b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f8a02f568e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f8a062493a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007f8a0409c31e in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007f8a0621f712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f8a0621fae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f8a06221c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#29 0x00007f89fb695cd3 in kdemain () from /usr/lib64/libkdeinit4_konqueror.so
#30 0x0000000000406f88 in _start ()

This bug may be a duplicate of or related to bug 235615

Reported using DrKonqi
Comment 1 Maksim Orlovich 2010-06-14 16:45:25 UTC
Hi... Thank you for your bug report. Unfortunately, there isn't really enough information here for us to do anything... You don't seem to have a way of reproducing it, and the backtrace... well, it's lying :( Basically, all of the 'KConfigGroup::writeEntry' items are bogus, so they don't give any idea on what's going on. Hmm, one of your earlier reports has a URL though, that may be diagnosable...
Comment 2 RGBl 2010-06-14 17:12:34 UTC
So Dr Konqui could be a liar... :(
I retrieved some links that were open at the time if they are of any use:
http://www.metalitalia.com/
http://www.concertionline.com/concerti-rock/steve-miller-band-unico-concerto-a-milano-per-ottobre/
http://www.concertionline.com/concerti-metal/alestorm-il-folkpower-metal-scozzese-allalcatraz-di-milano-in-concerto-a-ottobre/

I don't know what triggered the crash, because konqueror can go on for a while with these pages without crashing.

(off-topic: I'm not a fan of heavy metal. I was searching concerts for my crazy sister that will come to Italy to visit me... maybe my mood affected konqueror... ;) )
Comment 3 Andrew Crouthamel 2018-09-20 22:04:09 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 set the bug status 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 4 Andrew Crouthamel 2018-10-21 04:58:24 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!