Bug 181485 - random SIGSEGV on page load
Summary: random SIGSEGV on page load
Status: RESOLVED DUPLICATE of bug 165732
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-21 11:05 UTC by Julien Etienne
Modified: 2009-03-13 14:02 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 Julien Etienne 2009-01-21 11:05:49 UTC
Version:           4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 76.2" (using 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 76.2", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.7-9-default

After submitting a form on a SSL website, konqueror crashes with the following backtrace:
Application: Konqueror (konqueror), signal SIGSEGV
[Current thread is 1 (Thread 0xb5f72700 (LWP 6227))]
Thread 1 (Thread 0xb5f72700 (LWP 6227)):
[KCrash Handler]
#6 0xb7377321 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#7 0xb6dd6217 in QLineEdit::editingFinished() () from /usr/lib/libQtGui.so.4
#8 0xb6ddeec8 in QLineEdit::keyPressEvent(QKeyEvent*) () from /usr/lib/libQtGui.so.4
#9 0xb79d284d in KLineEdit::keyPressEvent(QKeyEvent*) () from /usr/lib/libkdeui.so.5
#10 0xb40cb9dc in khtml::RenderWidget::EventPropagator::sendEvent(QEvent*) () from /usr/lib/libkhtml.so.5
#11 0xb40cefbc in khtml::RenderWidget::handleEvent(DOM::EventImpl const&) () from /usr/lib/libkhtml.so.5
#12 0xb4048023 in DOM::HTMLGenericFormElementImpl::defaultEventHandler(DOM::EventImpl*) () from /usr/lib/libkhtml.so.5
#13 0xb40564e2 in DOM::HTMLInputElementImpl::defaultEventHandler(DOM::EventImpl*) () from /usr/lib/libkhtml.so.5
#14 0xb3fdd92a in DOM::NodeImpl::dispatchGenericEvent(DOM::EventImpl*, int&) () from /usr/lib/libkhtml.so.5
#15 0xb3fddb46 in DOM::NodeImpl::dispatchEvent(DOM::EventImpl*, int&, bool) () from /usr/lib/libkhtml.so.5
#16 0xb3fde41c in DOM::NodeImpl::dispatchKeyEvent(QKeyEvent*, bool) () from /usr/lib/libkhtml.so.5
#17 0xb3f4050e in KHTMLView::dispatchKeyEventHelper(QKeyEvent*, bool) () from /usr/lib/libkhtml.so.5
#18 0xb3f4409e in KHTMLView::dispatchKeyEvent(QKeyEvent*) () from /usr/lib/libkhtml.so.5
#19 0xb3f4f7ab in KHTMLView::keyPressEvent(QKeyEvent*) () from /usr/lib/libkhtml.so.5
#20 0xb3f4d644 in KHTMLView::eventFilter(QObject*, QEvent*) () from /usr/lib/libkhtml.so.5
#21 0xb7360b3a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#22 0xb6a3a8da in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#23 0xb6a43836 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb78ff8fd in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#25 0xb7361961 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#26 0xb6a9b4be in ?? () from /usr/lib/libQtGui.so.4
#27 0xb6ad0470 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb6ad2606 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb6aaabd5 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#30 0xb6ad408a in ?? () from /usr/lib/libQtGui.so.4
#31 0xb62ff9a8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb6303063 in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb6303221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb738bfb8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0xb6ad3785 in ?? () from /usr/lib/libQtGui.so.4
#36 0xb736001a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#37 0xb73601da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#38 0xb7362895 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#39 0xb6a3a777 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#40 0xb802667f in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#41 0x08048772 in main ()

If I come back after the crash to try again, it works.
But I get the same crash again on other pages (without being able to predict it).

It always occured on https websites, but I am not sure it is related as I mostly view https websites.

I browse the same websites with kde 3.5 without any issue/crash.
Comment 1 Dario Andres 2009-01-21 15:55:36 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Julien Etienne 2009-01-23 16:05:12 UTC
Unfortunately I am not able to follow the guidelines to get a more detailed report as I am not able to reproduce it systematically nor to get a proper live cd to get more debug information.

Another point I would like to point is that I am using the unofficial KDE Live CD provided here: http://home.kde.org/~binner/kde-four-live/
It is very helpful to test the upcoming kde version, but it would be even more useful to you if you provided an official live cd/dvd with all the debug information you need to help testing.

Last it would be a good idea to add a button to report the bug directly in the database from the crash handler (with necessary details), rather than having to restart the application and chose "Help>Report Bug".

I had another crash with plasma yesterday, but this time with even less information in the stack trace.

I hope other reports will be more helpful.
Best Regards,
Julien
Comment 3 Dario Andres 2009-01-25 18:48:42 UTC
@Julien: the debug information is too big to fit in a CD (may be a DVD).

This report may be related to bug 165732

Did you do something similar as reported in bug 165732 (and bug 165732 comment 2). If you did, this is a duplicate of that bug

Thanks :)
Comment 4 Jonathan Thomas 2009-03-13 14:02:52 UTC

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