Bug 53054 - Cache cleaner crash (on konqueror exit)
Summary: Cache cleaner crash (on konqueror exit)
Status: RESOLVED DUPLICATE of bug 53520
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 4.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-16 11:09 UTC by Michael Goffioul
Modified: 2003-06-15 00:59 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 Michael Goffioul 2003-01-16 11:09:53 UTC
Version:           4.0 (using KDE 3.1.9)
Compiler:          gcc version 3.1 (Mandrake Linux 8.3 3.1-0.12mdk)
OS:          Linux (i686) release 2.4.18-5mdk

Since about 2 days, konqueror crashes on exit. I cleaned the build tree, deleted my whole kde
installation, and recompile/reinstall everything, the problem is still there. Here's the backtrace:

[New Thread 1024 (LWP 12122)]
0x410cf1d9 in wait4 () from /lib/libc.so.6
#0  0x410cf1d9 in wait4 () from /lib/libc.so.6
#1  0x4114cef8 in __check_rhosts_file () from /lib/libc.so.6
#2  0x40f099f6 in waitpid (pid=12135, stat_loc=0x0, options=0)
    at wrapsyscall.c:172
#3  0x40670749 in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#4  0x40f073ab in pthread_sighandler (signo=6, ctx=
      {gs = 0, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 49168, edi = 1089521312, esi = 12122, ebp = 3221219528, esp = 3221219484, ebx = 12122, edx = 1089548156, ecx = 6, eax = 0, trapno = 0, err = 0, eip = 1090791793, cs = 35, __csh = 0, eflags = 582, esp_at_signal = 3221219484, ss = 43, __ssh = 0, fpstate = 0xbfffe620, oldmask = 2147483648, cr2 = 0}) at signals.c:97
#5  0x410427c8 in killpg () from /lib/libc.so.6
#6  0x41043da3 in abort () from /lib/libc.so.6
#7  0x4103c162 in __assert_fail () from /lib/libc.so.6
#8  0x418967f5 in khtml::Cache::clear() () from /opt/kde3/lib/libkhtml.so.4
#9  0x417da574 in KHTMLFactory::~KHTMLFactory() ()
   from /opt/kde3/lib/libkhtml.so.4
#10 0x417da7cc in KHTMLFactory::deref() () from /opt/kde3/lib/libkhtml.so.4
#11 0x417da442 in KHTMLFactory::~KHTMLFactory() ()
   from /opt/kde3/lib/libkhtml.so.4
#12 0x406882be in KLibrary::~KLibrary() () from /opt/kde3/lib/libkdecore.so.4
#13 0x4068927c in KLibrary::slotTimeout() () from /opt/kde3/lib/libkdecore.so.4
#14 0x4068bc49 in KLibrary::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/libkdecore.so.4
#15 0x409d5d9b in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /opt/qt3/lib/libqt-mt.so.3
#16 0x409d5c40 in QObject::activate_signal(int) ()
   from /opt/qt3/lib/libqt-mt.so.3
#17 0x40c8a4a5 in QTimer::timeout() () from /opt/qt3/lib/libqt-mt.so.3
#18 0x409f425b in QTimer::event(QEvent*) () from /opt/qt3/lib/libqt-mt.so.3
#19 0x4097c5e1 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /opt/qt3/lib/libqt-mt.so.3
#20 0x4097be5c in QApplication::notify(QObject*, QEvent*) ()
   from /opt/qt3/lib/libqt-mt.so.3
#21 0x405e4e94 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkdecore.so.4
#22 0x40959843 in QEventLoop::activateTimers() ()
   from /opt/qt3/lib/libqt-mt.so.3
#23 0x4093975f in QEventLoop::processEvents(unsigned) ()
   from /opt/qt3/lib/libqt-mt.so.3
#24 0x4098ed9f in QEventLoop::enterLoop() () from /opt/qt3/lib/libqt-mt.so.3
#25 0x4098ec54 in QEventLoop::exec() () from /opt/qt3/lib/libqt-mt.so.3
#26 0x4097c821 in QApplication::exec() () from /opt/qt3/lib/libqt-mt.so.3
#27 0x41309619 in main () from /opt/kde3/lib/konqueror.so
#28 0x0804cbbf in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#29 0x0804d7bb in handle_launcher_request(int) ()
#30 0x0804dc5a in handle_requests(int) ()
#31 0x0804e90a in main ()
#32 0x410305b0 in __libc_start_main () from /lib/libc.so.6
Comment 1 Dirk Mueller 2003-01-31 02:29:57 UTC
which pages do you view before you close the window ? 
 
does the problem still exist? there was a problem in CVS HEAD for a few 
days, but its fixed for quite some time already.. 
 
Comment 2 Michael Goffioul 2003-01-31 10:54:13 UTC
Well, I noticed previously that it only happens whatever the web site, but only 
with my auto-proxy JS script. I changed proxy configuration to use manual 
config, and the problem disappeared. Now I just tried again with my proxy script, 
it simply doesn't work. Debug tells me 
 
KJS: Failed function call attempt on:  : Object (0x81407e0), line 3 
 
If you want my proxy script, I'll send it to you privately. I'm using CVS from 
wednesday night. 
 
Michael. 
Comment 3 Dirk Mueller 2003-02-05 00:08:51 UTC
I've fixed a crash related to auto proxy code. 
 
if it still happens, I'd like to have a way to reproduce it :) its really difficult to fix 
otherwise.  
Comment 4 Michael Goffioul 2003-02-05 10:36:55 UTC
I don't experience any crash anoymore, but the proxy script stuff doesn't
work anymore. Each time it tries to execute it, the debug output looks
like:

KJS: Failed function call attempt on:  : Object (0x811bb20), line 3
KJS: Failed function call attempt on:  : Object (0x8119d98), line 3
KJS: Failed function call attempt on:  : Object (0x811c190), line 3

I send you my proxy script by private mail.

Michael.
Comment 5 Kai Lahmann 2003-06-15 00:59:43 UTC

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