Bug#401995: iceape: hangs on modal dialogs and message boxes
Wladimir Mutel
mwg at mwg.dp.ua
Tue Jan 16 23:25:10 CET 2007
On Tue, Jan 16, 2007 at 08:04:09PM +0100, Mike Hommey wrote:
> > Could you propose any guesses ?
> Unfortunatelly, there's nothing informative enough to do any guess :(
> Could you try to run iceape normally and attach gdb to its pid when it
> hangs ?
I had done exactly that. Run iceape, then attached gdb to
iceape-bin process, and very soon it hung.
Backtrace was even less helpful (thread apply all bt) :
Thread 32 (Thread -1269912656 (LWP 15527)):
#0 0xb7fbf410 in ?? ()
#1 0xb44ea058 in ?? ()
#2 0x00000001 in ?? ()
#3 0x00000000 in ?? ()
Thread 31 (Thread -1291469904 (LWP 15524)):
#0 0xb7fbf410 in ?? ()
#1 0xb305abc8 in ?? ()
#2 0x00000007 in ?? ()
#3 0x00000000 in ?? ()
Thread 30 (Thread -1281279056 (LWP 15523)):
#0 0xb7fbf410 in ?? ()
#1 0xb3a1336c in ?? ()
#2 0x000025a5 in ?? ()
#3 0x00000000 in ?? ()
Thread 28 (Thread -1314915408 (LWP 15521)):
#0 0xb7fbf410 in ?? ()
#1 0xb19ff36c in ?? ()
#2 0x000025e1 in ?? ()
#3 0x00000000 in ?? ()
Thread 22 (Thread -1305085008 (LWP 15384)):
#0 0xb7fbf410 in ?? ()
#1 0xb235ef68 in ?? ()
#2 0x00000071 in ?? ()
#3 0x00000000 in ?? ()
Thread 4 (Thread -1225167952 (LWP 14026)):
#0 0xb7fbf410 in ?? ()
#1 0xb6f95ce8 in ?? ()
#2 0x00000001 in ?? ()
#3 0x00000000 in ?? ()
Thread 2 (Thread -1256887376 (LWP 14028)):
#0 0xb7fbf410 in ?? ()
#1 0xb51563e8 in ?? ()
#2 0x001a305b in ?? ()
#3 0x00000000 in ?? ()
Thread 1 (Thread -1220061504 (LWP 14018)):
#0 0xb7fbf410 in ?? ()
#1 0xbfc1c81c in ?? ()
#2 0x00000011 in ?? ()
#3 0x00000000 in ?? ()
strace shows futex syscall in progress, as usual.
Is something wrong with my system ?
Nobody other seems to report this behaviour...
Other software runs on my system pretty well,
except 'trafshow' program from 'netdiag' package which sometimes
(quite often) hangs with similar symptoms. I think this is
related to async DNS resolving done inside it (with -n, it does
not hang ever). May be some userspace data representing futex
are corrupted that causes the syscall hang ?
More information about the pkg-mozilla-maintainers
mailing list