Bug 114626 - Konqueror crashes when clicking on a link on Memigo.com
Summary: Konqueror crashes when clicking on a link on Memigo.com
Status: RESOLVED DUPLICATE of bug 113600
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: 2005-10-18 19:20 UTC by Henk Poley
Modified: 2005-12-14 12:21 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 Henk Poley 2005-10-21 00:21:50 UTC
Ah.. bugs.kde.org was kind of unresponsive whe I posted this. Apparently it processed half of the request. Here's a copy of my report.

I think it's still against KDE 3.5 beta1 (though I did compile beta2 right away when it was available)

--

If you have an account on Memigo.com you get a personalised list of news. When you click a newsitem, it is loaded with a frame on the bottom. This frame contains basicly 2 elements, a link back to memigo (normal link), and a rating bar (has some Javascript).

What probably happened is that I clicked the rating bar and immediately thereafter pressed the link back to memigo. Which broke something in the KJS.

Backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1229678400 (LWP 16520)]
[KCrash handler]
#4  0x08054084 in ?? ()
#5  0xb72a766b in qt_inheritedBy (superClass=0x8366398, object=0x885ab98)
    at qobject.cpp:596
#6  0xb66603d7 in qt_cast<KHTMLPart*> (object=0x885ab98) at qobjectdefs.h:173
#7  0xb655ed10 in KJS::Window::retrieve (p=0x885ab98) at kjs_window.cpp:373
#8  0xb655ec7d in KJS::Window::retrieveWindow (p=0x885ab98)
    at kjs_window.cpp:343
#9  0xb64384ac in KHTMLPart::begin (this=0x893b208, url=@0x8794820, 
    xOffset=171321657, yOffset=171321657) at khtml_part.cpp:1884
#10 0xb64369af in KHTMLPart::slotData (this=0x893b208, kio_job=0x9c5b450, 
    data=@0xbfca790c) at khtml_part.cpp:1578
#11 0xb644fe40 in KHTMLPart::qt_invoke (this=0x893b208, _id=16, _o=0xbfca7568)
    at qucom_p.h:312
#12 0xb72aa053 in QObject::activate_signal (this=0x9c5b450, clist=0x8652900, 
    o=0xbfca7568) at qconnection.h:56
#13 0xb7dc0fcd in KIO::TransferJob::data (this=0x9c5b450, t0=0x9c5b450, 
    t1=@0xbfca790c) at jobclasses.moc:993
#14 0xb7db00f4 in KIO::TransferJob::slotData (this=0x9c5b450, 
    _data=@0xbfca790c) at job.cpp:900
#15 0xb7dc13fd in KIO::TransferJob::qt_invoke (this=0x9c5b450, _id=18, 
    _o=0xbfca7664) at qucom_p.h:312
#16 0xb72aa053 in QObject::activate_signal (this=0xa4dfc58, clist=0xa2d01d8, 
    o=0xbfca7664) at qconnection.h:56
#17 0xb7da51e3 in KIO::SlaveInterface::data (this=0xa4dfc58, t0=@0xbfca790c)
    at slaveinterface.moc:194
#18 0xb7da3c79 in KIO::SlaveInterface::dispatch (this=0xa4dfc58, _cmd=100, 
    rawdata=@0xbfca790c) at slaveinterface.cpp:234
#19 0xb7da3a2f in KIO::SlaveInterface::dispatch (this=0xa4dfc58)
    at slaveinterface.cpp:173
#20 0xb7da1d21 in KIO::Slave::gotInput (this=0xa4dfc58) at slave.cpp:300
#21 0xb7da3351 in KIO::Slave::qt_invoke (this=0xa4dfc58, _id=4, _o=0xbfca7a08)
    at slave.moc:113
#22 0xb72aa053 in QObject::activate_signal (this=0x8f96578, clist=0x9941d30, 
    o=0xbfca7a08) at qconnection.h:56
#23 0xb72aa1ad in QObject::activate_signal (this=0x8f96578, signal=2, 
    param=142165864) at qobject.cpp:2448
#24 0xb75dec72 in QSocketNotifier::activated (this=0xa362939, t0=171321657)
    at qmetaobject.h:261
#25 0xb72c616e in QSocketNotifier::event (this=0x8f96578, e=0xbfca7e10)
    at qsocketnotifier.cpp:258
#26 0xb724eb3c in QApplication::internalNotify (this=0xa362939, 
    receiver=0x8f96578, e=0xbfca7e10) at qapplication.cpp:2615
#27 0xb724dedd in QApplication::notify (this=0xbfca8394, receiver=0x8f96578, 
    e=0xbfca7e10) at qapplication.cpp:2372
#28 0xb78b0d34 in KApplication::notify (this=0xbfca8394, receiver=0x8f96578, 
    event=0xbfca7e10) at kapplication.cpp:550
#29 0xb723e795 in QEventLoop::activateSocketNotifiers (this=0x815d5b8)
    at qeventloop_unix.cpp:579
#30 0xb71f887f in QEventLoop::processEvents (this=0x815d5b8, flags=4)
    at qeventloop_x11.cpp:383
#31 0xb7260a98 in QEventLoop::enterLoop (this=0x815d5b8) at qeventloop.cpp:198
#32 0xb7260948 in QEventLoop::exec (this=0x815d5b8) at qeventloop.cpp:145
#33 0xb724ed71 in QApplication::exec (this=0xbfca8394)
    at qapplication.cpp:2758
#34 0xb6a59ca4 in kdemain (argc=3, argv=0x80849d8) at konq_main.cc:206
#35 0xb77b57fe in kdeinitmain (argc=3, argv=0x80849d8) at konqueror_dummy.cc:3
#36 0x0804cf38 in launch (argc=3, _name=0x813a34c "konqueror", 
    args=0x813a396 "", cwd=0x0, envc=0, envs=0x813a39a "", reset_env=false, 
    tty=0x0, avoid_loops=false, startup_id_str=0x804f617 "0") at kinit.cpp:637
#37 0x0804db23 in handle_launcher_request (sock=8) at kinit.cpp:1201
#38 0x0804df7d in handle_requests (waitForPid=0) at kinit.cpp:1404
#39 0x0804ed6e in main (argc=2, argv=0xbfca89e4, envp=0xbfca89f0)
    at kinit.cpp:1848
Comment 1 Maksim Orlovich 2005-10-21 01:20:03 UTC
That should be fixed in b2
Comment 2 Tommi Tervo 2005-12-14 12:21:31 UTC

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