Bug 121934

Summary:	Konqueror crash on www.drudgereport.com site (testcase)
Product:	[Applications] konqueror	Reporter:	Philippe Rigault <prigault>
Component:	general	Assignee:	Konqueror Bugs <konqueror-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	The HTML page causing the crash

Description Philippe Rigault 2006-02-14 01:56:11 UTC

Version:           3.5.1 (using KDE 3.5.1, compiled sources)
Compiler:          gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
OS:                Linux (x86_64) release 2.6.12-1.1381_FC3

Since the site changes very often, I attach below a copy of the front page that makes it crash for me.

How to reproduce:

1. Open attachment in konqueror
2. Click on 'WHITE HOUSE GRILLED OVER CHENEY HUNTING ACCIDENT'

-> Crash (Konqui shot by Dick Cheney too!)

Backtrace:

Using host libthread_db library "/lib64/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912567508512 (LWP 25601)]
[KCrash handler]
#5  0x00002aaab34628ea in fillStructuresUsingTimeArgs ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#6  0x00002aaab347d630 in KJS::DateProtoFuncImp::call ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#7  0x00002aaab347a978 in KJS::Object::call ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#8  0x00002aaab3485b7e in KJS::FunctionCallNode::evaluate ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#9  0x00002aaab3483196 in KJS::ExprStatementNode::execute ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#10 0x00002aaab34807c9 in KJS::SourceElementsNode::execute ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#11 0x00002aaab346ad19 in KJS::BlockNode::execute ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#12 0x00002aaab348be8e in KJS::InterpreterImp::evaluate ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#13 0x00002aaab348c4fd in KJS::Interpreter::evaluate ()
   from /opt/kde3.5.1/lib64/libkjs.so.1
#14 0x00002aaab321386b in KJS::KJSProxyImpl::evaluate ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#15 0x00002aaab3083967 in KHTMLPart::executeScript ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#16 0x00002aaab30cc2ea in khtml::HTMLTokenizer::scriptExecution ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#17 0x00002aaab30f3a41 in khtml::HTMLTokenizer::scriptHandler ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#18 0x00002aaab30f49d5 in khtml::HTMLTokenizer::parseSpecial ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#19 0x00002aaab30f5a0b in khtml::HTMLTokenizer::parseTag ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#20 0x00002aaab30f748e in khtml::HTMLTokenizer::write ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#21 0x00002aaab30f3621 in khtml::HTMLTokenizer::notifyFinished ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#22 0x00002aaab31a1ac1 in khtml::CachedScript::checkNotify ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#23 0x00002aaab31a1d1c in khtml::CachedScript::data ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#24 0x00002aaab31a2d3b in khtml::Loader::slotFinished ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#25 0x00002aaab31a2ef5 in khtml::Loader::qt_invoke ()
   from /opt/kde3.5.1/lib64/libkhtml.so.4
#26 0x00002aaaac871898 in QObject::activate_signal ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#27 0x00002aaaaaeb6406 in KIO::Job::result ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#28 0x00002aaaaaee1ba3 in KIO::Job::emitResult ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#29 0x00002aaaaaf0c876 in KIO::SimpleJob::slotFinished ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#30 0x00002aaaaaf0ce9a in KIO::TransferJob::slotFinished ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#31 0x00002aaaaaee1779 in KIO::TransferJob::qt_invoke ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#32 0x00002aaaac871898 in QObject::activate_signal ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#33 0x00002aaaac872002 in QObject::activate_signal ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#34 0x00002aaaaaf00395 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#35 0x00002aaaaaedf0b6 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#36 0x00002aaaaaed4617 in KIO::Slave::gotInput ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#37 0x00002aaaaaedc33b in KIO::Slave::qt_invoke ()
   from /opt/kde3.5.1/lib64/libkio.so.4
#38 0x00002aaaac871898 in QObject::activate_signal ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#39 0x00002aaaac871e9f in QObject::activate_signal ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#40 0x00002aaaac88a09b in QSocketNotifier::event ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#41 0x00002aaaac81896d in QApplication::internalNotify ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#42 0x00002aaaac818b15 in QApplication::notify ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#43 0x00002aaaabc5f351 in KApplication::notify ()
   from /opt/kde3.5.1/lib64/libkdecore.so.4
#44 0x00002aaaac80dbef in QEventLoop::activateSocketNotifiers ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#45 0x00002aaaac7cdf58 in QEventLoop::processEvents ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#46 0x00002aaaac82c9a5 in QEventLoop::enterLoop ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#47 0x00002aaaac82c902 in QEventLoop::exec ()
   from /opt/kde3.5.1/lib64/libqt-mt.so.3
#48 0x00002aaab22b383a in kdemain ()
   from /opt/kde3.5.1/lib64/libkdeinit_konqueror.so
#49 0x0000000000407b58 in launch ()
#50 0x00000000004083d7 in handle_launcher_request ()
#51 0x0000000000408a05 in handle_requests ()
#52 0x0000000000409198 in main ()

Comment 1 Philippe Rigault 2006-02-14 01:57:34 UTC

Created attachment 14680 [details]
The HTML page causing the crash

Comment 2 Philippe Rigault 2006-02-14 01:59:56 UTC

It looks like typing the link address in the Location bar causes the crash too:
http://www.cbsnews.com/stories/2006/02/13/national/main1309344.shtml

Comment 3 George Staikos 2006-02-14 02:00:51 UTC


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

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

Comment 4 Maksim Orlovich 2006-02-14 02:02:41 UTC

Can't confirm, though given the bt, it suggests a date function was given funny info. Probably highly sensitive to tons of stuff.

And do you get a crash on cbsnews.com frontpage as well?



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

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

Comment 5 Philippe Rigault 2006-02-14 02:16:07 UTC

> And do you get a crash on cbsnews.com frontpage as well? 

Yes I do.

Comment 6 Maksim Orlovich 2006-02-14 02:49:25 UTC

Thanks, we have an another report of crashes on that site that lacks a useful backtrace --- and this suggests it's probably the same issue.