Bug 191289 - repeatable crash on Blogger.com "Manage Posts" page
Summary: repeatable crash on Blogger.com "Manage Posts" page
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 4.2.2
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-01 21:52 UTC by skierpage
Modified: 2011-07-25 11:45 UTC (History)
3 users (show)

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


Attachments
KDE Crash Handler trace from Blogger Edit Posts screen (4.31 KB, text/plain)
2009-05-15 02:15 UTC, skierpage
Details

Note You need to log in before you can comment on or make changes to this bug.
Description skierpage 2009-05-01 21:52:01 UTC
Version:           4.2.2 (KDE 4.2.2) (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-11-generic

I use Blogger to publish my blog.  Every time I go to Its Manage Posts page, Konqueror crashes 5-20 seconds later with SIGSEGV.  It crashes even if I don't interact with it; when I let Konq restore an old session it crashed before I viewed that tab.  If I do view the tab it seems to display fine.  I have hundreds but not thousands of blog posts.

I use a pretty stock Konq; I installed flashplugin, changed one keyboard shortcut, etc.

Crash Handler says "This backtrace appears to be of no use"
Comment 1 FiNeX 2009-05-02 11:53:01 UTC
If you want, you can install the debug pacakges in order to give us a useful backtrace. On kubuntu you should look for -dbg packages.
Comment 2 A. Spehr 2009-05-07 14:05:28 UTC
What is the exact url it crashes on? I don't see any such "key".
Comment 3 skierpage 2009-05-15 02:13:41 UTC
(In reply to comment #2)
> What is the exact url it crashes on? I don't see any such "key".

Logging in to blogger.com usually takes you to a Dashboard.  Under "Manage Blogs" click _Edit Posts_ (damn web apps keep changing their UI :-) ).  That takes you to http://www.blogger.com/posts.g?blogID=NNNNN depending on your blogID.

Kubuntu 9.04 updated me to KDE 4.2.3, I installed the -dbg packages.  At first I didn't see the bug.  But when I changed to show 300 posts (I have about 250) and searched for a common word "the", a few seconds later I got the crash.  The crash handler listed.

#5  0x00007f4b6e72b0a0 in typeinfo name for QTextBlockGroupPrivate () from /usr/lib/libQtGui.so.4 
... from KonqView::updateHistoryEntry 

I'll attach the entire trace.
Comment 4 skierpage 2009-05-15 02:15:33 UTC
Created attachment 33672 [details]
KDE Crash Handler trace from Blogger Edit Posts screen
Comment 5 Pino Toscano 2009-05-15 02:23:56 UTC
Pasting the backtrace of comment #4:

Application: Konqueror (konqueror), signal SIGSEGV
0x00007f4b6c54bd21 in nanosleep () from /lib/libc.so.6
Current language:  auto; currently c

Thread 1 (Thread 0x7f4b71664750 (LWP 6192)):
[KCrash Handler]
#5  0x00007f4b6e72b0a0 in typeinfo name for QTextBlockGroupPrivate () from /usr/lib/libQtGui.so.4
#6  0x00007f4b61db5caa in DOM::HTMLSelectElementImpl::state (this=<value optimized out>) at /build/buildd/kde4libs-4.2.3/khtml/html/html_formimpl.cpp:2277
#7  0x00007f4b61d3a07b in DOM::DocumentImpl::docState (this=<value optimized out>) at /build/buildd/kde4libs-4.2.3/khtml/xml/dom_docimpl.cpp:1338
#8  0x00007f4b61ccde8c in KHTMLPart::saveState (this=0x2324d10, stream=@0x7fff79695240) at /build/buildd/kde4libs-4.2.3/khtml/khtml_part.cpp:5221
#9  0x00007f4b711c94c0 in KonqView::updateHistoryEntry (this=0x232bef0, saveLocationBarURL=true) at /build/buildd/kdebase-4.2.3/apps/konqueror/src/konqview.cpp:773
#10 0x00007f4b711cbcfd in KonqView::slotCompleted (this=0x232bef0, hasPending=false) at /build/buildd/kdebase-4.2.3/apps/konqueror/src/konqview.cpp:609
#11 0x00007f4b711cc7cd in KonqView::qt_metacall (this=0x232bef0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff796954c0)
    at /build/buildd/kdebase-4.2.3/obj-x86_64-linux-gnu/apps/konqueror/src/konqview.moc:121
#12 0x00007f4b6ec7c8d2 in QMetaObject::activate (sender=0x2324d10, from_signal_index=<value optimized out>, to_signal_index=8, argv=0x43620a0) at kernel/qobject.cpp:3120
#13 0x00007f4b61cb7dd1 in KHTMLView::timerEvent (this=0x237f2c0, e=<value optimized out>) at /build/buildd/kde4libs-4.2.3/khtml/khtmlview.cpp:4292
#14 0x00007f4b6ec76bb3 in QObject::event (this=0x237f2c0, e=0x0) at kernel/qobject.cpp:1082
#15 0x00007f4b6e10b61d in QWidget::event (this=0x237f2c0, event=0x7fff79696000) at kernel/qwidget.cpp:7918
#16 0x00007f4b6e4a945b in QFrame::event (this=0x237f2c0, e=0x7fff79696000) at widgets/qframe.cpp:559
#17 0x00007f4b6e53aa89 in QAbstractScrollArea::event (this=0x237f2c0, e=0x7fff79696000) at widgets/qabstractscrollarea.cpp:918
#18 0x00007f4b61cba931 in KHTMLView::event (this=0x237f2c0, e=0x7fff79696000) at /build/buildd/kde4libs-4.2.3/khtml/khtmlview.cpp:590
#19 0x00007f4b6e0bab9d in QApplicationPrivate::notify_helper (this=0x1ab1430, receiver=0x237f2c0, e=0x7fff79696000) at kernel/qapplication.cpp:4057
#20 0x00007f4b6e0c2dea in QApplication::notify (this=0x7fff79696520, receiver=0x237f2c0, e=0x7fff79696000) at kernel/qapplication.cpp:4022
#21 0x00007f4b6fa958db in KApplication::notify (this=0x7fff79696520, receiver=0x237f2c0, event=0x7fff79696000) at /build/buildd/kde4libs-4.2.3/kdeui/kernel/kapplication.cpp:307
#22 0x00007f4b6ec66dfc in QCoreApplication::notifyInternal (this=0x7fff79696520, receiver=0x237f2c0, event=0x7fff79696000) at kernel/qcoreapplication.cpp:610
#23 0x00007f4b6ec93eb6 in QTimerInfoList::activateTimers (this=0x1ab5080) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#24 0x00007f4b6ec905cd in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#25 0x00007f4b6a24d20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0x00007f4b6a2508e0 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0x00007f4b6a250a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0x00007f4b6ec9052f in QEventDispatcherGlib::processEvents (this=0x1a9cb50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#29 0x00007f4b6e15370f in QGuiEventDispatcherGlib::processEvents (this=0x2911b10, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x00007f4b6ec656a2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 2036949616}) at kernel/qeventloop.cpp:149
#31 0x00007f4b6ec65a6d in QEventLoop::exec (this=0x7fff796962b0, flags={i = 2036949696}) at kernel/qeventloop.cpp:200
#32 0x00007f4b6ec67d34 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x00007f4b7124b9e9 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdebase-4.2.3/apps/konqueror/src/konqmain.cpp:257
#34 0x00007f4b6c4c25a6 in __libc_start_main (main=0x400870 <main>, argc=2, ubp_av=0x7fff79696f98, init=0x4008a0 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff79696f88) at libc-start.c:220
#35 0x00000000004007a9 in _start () at ../sysdeps/x86_64/elf/start.S:113
Comment 6 Martin Koller 2011-07-25 11:45:16 UTC
does it still crash with KDE >= 4.6.5 ?