Bug 222333 - Konqueror crashed on click on bank https site close window button
Summary: Konqueror crashed on click on bank https site close window button
Status: RESOLVED DUPLICATE of bug 228255
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-12 05:21 UTC by Clemens
Modified: 2010-02-25 16:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Clemens 2010-01-12 05:21:31 UTC
Application: konqueror (4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)))
KDE Platform Version: 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1))
Qt Version: 4.6.0
Operating System: Linux 2.6.31-18-generic x86_64
Distribution: Ubuntu 9.10

-- Information about the crash:
Segmentation fault behaviour has been observed on several sites using html 'close window' button. Bank https site provides 'close window' button and Konqueror crashes in multi and single tab configurations.

The crash can be reproduced every time.

 -- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f331f021d37 in operator<<(QDebug, QObject const*) () from /usr/lib/libQtCore.so.4
#6  0x00007f33201a1c30 in KParts::StatusBarExtension::removeStatusBarItem(QWidget*) () from /usr/lib/libkparts.so.4
#7  0x00007f330d170c91 in KHTMLPart::slotWalletClosed() () from /usr/lib/libkhtml.so.5
#8  0x00007f330d1824fb in KHTMLPart::~KHTMLPart() () from /usr/lib/libkhtml.so.5
#9  0x00007f331f01ad3d in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#10 0x00007f331e1b0e8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#11 0x00007f331e1b748d in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#12 0x00007f331f54fe16 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#13 0x00007f331f00b04c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#14 0x00007f331f00d7c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#15 0x00007f331f034ae3 in ?? () from /usr/lib/libQtCore.so.4
#16 0x00007f331a650bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#17 0x00007f331a654598 in ?? () from /lib/libglib-2.0.so.0
#18 0x00007f331a6546c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#19 0x00007f331f034623 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#20 0x00007f331e25f2fe in ?? () from /usr/lib/libQtGui.so.4
#21 0x00007f331f009972 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#22 0x00007f331f009d4c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0x00007f331f00da8b in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#24 0x00007f331467b7a6 in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#25 0x0000000000406fb8 in _start ()

Reported using DrKonqi
Comment 1 Maksim Orlovich 2010-01-12 18:49:27 UTC
Hi... Thanks for the report. It would be very helpful if you could provide a bit more information (as we obviously can't test it ourselves in this case). 
In particular:
1) Please install debug packages as described here:
http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports
so we get line # information on backtraces
2) Install valgrind, from your distro's packages
3) Run "valgrind konqueror --num-callers=32 &>log" from a terminal, and try to reproduce the bug, then attach the log file here. It'll be quite slow, but it will likely diagnose exactly what's going on wrong.

Thanks again!
Comment 2 Dario Andres 2010-02-17 14:15:37 UTC
@Maksim: are bug 223739 and bug 227360 also related to this? (seems so) Regards
Comment 3 Maksim Orlovich 2010-02-25 16:58:36 UTC

*** This bug has been marked as a duplicate of bug 228255 ***