Bug 104665 - crash when switching between tabs with opened articles and back button
Summary: crash when switching between tabs with opened articles and back button
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-27 17:51 UTC by Carsten Lohrke
Modified: 2005-04-28 13:48 UTC (History)
0 users

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 Carsten Lohrke 2005-04-27 17:51:33 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages

1) I clicked on the full text link of a feed entry to open a tab with the full article
2) I followed a link in the open web page
3) same as in (1) with another article
4) back to the first openened tab and hit back button -> crash

[KCrash handler]
#5  0x413f9dba in QTimer::stop () from /usr/qt/3/lib/libqt-mt.so.3
#6  0x401145b1 in KHTMLPart::openURL (this=0x81f0a30, url=@0xbfffdb80)
    at khtml_part.cpp:550
#7  0x42107aa0 in Akregator::BrowserRun::foundMimeType ()
   from /usr/kde/3.4/lib/kde3/libakregatorpart.so
#8  0x408aefce in KParts::BrowserRun::slotBrowserMimetype (this=0x874fc90, 
    _job=0x8750a08, type=@0x8752618) at browserrun.cpp:196
#9  0x408b0f02 in KParts::BrowserRun::qt_invoke (this=0x874fc90, 
    _id=141895192, _o=0xbfffdd10) at browserrun.moc:102
#10 0x42107c4b in Akregator::BrowserRun::qt_invoke ()
   from /usr/kde/3.4/lib/kde3/libakregatorpart.so
#11 0x413d8374 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#12 0x409c8dd5 in KIO::TransferJob::mimetype (this=0x8750a08, t0=0xf0, 
    t1=@0xf0) at jobclasses.moc:1029
#13 0x409c8e42 in KIO::TransferJob::slotMimetype (this=0x8750a08, type=@0xf0)
    at job.cpp:1039
#14 0x409ca3c1 in KIO::TransferJob::qt_invoke (this=0x8750a08, _id=20, 
    _o=0xbfffde30) at jobclasses.moc:1053
#15 0x413d8374 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#16 0x413d863a in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#17 0x409b670c in KIO::SlaveInterface::mimeType (this=0xf0, t0=@0xf0)
    at slaveinterface.moc:370
#18 0x409b7ade in KIO::SlaveInterface::dispatch (this=0x83e8aa8, _cmd=21, 
    rawdata=@0xbfffde30) at slaveinterface.cpp:338
#19 0x409b728b in KIO::SlaveInterface::dispatch (this=0x83e8aa8)
    at slaveinterface.cpp:173
#20 0x409b2fcd in KIO::Slave::gotInput (this=0x83e8aa8) at slave.cpp:300
#21 0x409b34e8 in KIO::Slave::qt_invoke (this=0x83e8aa8, _id=4, _o=0xbfffe230)
    at slave.moc:113
#22 0x413d8374 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#23 0x413d893a in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#24 0x4172b3a0 in QSocketNotifier::activated ()
   from /usr/qt/3/lib/libqt-mt.so.3
#25 0x413f4eff in QSocketNotifier::event () from /usr/qt/3/lib/libqt-mt.so.3
#26 0x4137578f in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#27 0x4137592c in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#28 0x40f055a1 in KApplication::notify (this=0xbfffe9d0, receiver=0x832fe88, 
    event=0xbfffe660) at kapplication.cpp:549
#29 0x41369083 in QEventLoop::activateSocketNotifiers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#30 0x41320f21 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#31 0x4138be30 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#32 0x4138bd86 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#33 0x4137493f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#34 0x080502cf in main ()
Comment 1 Eckhart Wörner 2005-04-27 18:26:55 UTC
Can you reproduce this bug? Is it only reproducable with a specific feed? I cannot reproduce it here (3.4 and CVS HEAD).
Comment 2 Carsten Lohrke 2005-04-27 19:07:23 UTC
Right now - no. It's just when you have the box under load and have tabs/windows opening, kioslaves loading data and performing actions in the toolbar in between it's possible to crash konqueror, too. See e.g. Bug 87495. I suppose there must be some racy code deep in the related libs.
Comment 3 Teemu Rytilahti 2005-04-28 13:48:41 UTC
This has been fixed after 3.4 release.