Bug#401995: iceape: hangs on modal dialogs and message boxes

2007-01-16 Thread Wladimir Mutel
Hi,

Same symptoms with iceape 1.0.7-2
LD_ASSUME_KERNEL=2.4.1 does not help
Being run with -debug option, iceape works more stable, in the
sense that it hangs later. Without debugger, it hangs quite
soon. Right when mail-news-related modal dialog is shown
(unknown/unverified/expired certificate, re-entry of mail server
password, etc).

Backtrace from gdb :
[BEGIN]
Thread 91 (Thread -1331692624 (LWP 6527)):
#0  0xb7fc4410 in ?? ()
#1  0xb09ff058 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 90 (Thread -1354200144 (LWP 6526)):
#0  0xb7fc4410 in ?? ()
#1  0xaf487bc8 in ?? ()
#2  0x0005 in ?? ()
#3  0x in ?? ()

Thread 89 (Thread -1275728976 (LWP 6525)):
#0  0xb7fc4410 in ?? ()
#1  0xb3f5e36c in ?? ()
#2  0x00021fe5 in ?? ()
#3  0x in ?? ()

Thread 87 (Thread -1321935952 (LWP 6523)):
#0  0xb7fc4410 in ?? ()
#1  0xb134d36c in ?? ()
#2  0x0002201b in ?? ()
#3  0x in ?? ()

Thread 79 (Thread -1308320848 (LWP 6448)):
#0  0xb7fc4410 in ?? ()
#1  0xb2048f68 in ?? ()
#2  0x0027 in ?? ()
#3  0x in ?? ()

Thread 28 (Thread -1248572496 (LWP 32498)):
#0  0xb7fc4410 in ?? ()
#1  0xb5943fe8 in ?? ()
#2  0x in ?? ()
#3  0x0001 in ?? ()
#4  0xb763c783 in poll () from /lib/tls/i686/cmov/libc.so.6
#5  0xb7e65ad9 in PR_Poll (pds=0xb5944420, npds=1, timeout=4294967295)
at ptio.c:3879
#6  0xb7e6c40c in WaitPidDaemonThread (unused=0x0) at uxproces.c:714
#7  0xb7e69cfc in _pt_root (arg=0x9dc4da0) at ptthread.c:220
#8  0xb7e25240 in start_thread () from
/lib/tls/i686/cmov/libpthread.so.0
#9  0xb764632e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 4 (Thread -1256965200 (LWP 32416)):
#0  0xb7fc4410 in ?? ()
#1  0xb51433e8 in ?? ()
#2  0x002bf2d7 in ?? ()
#3  0x in ?? ()

Thread 2 (Thread -1225147472 (LWP 32412)):
#0  0xb7fc4410 in ?? ()
#1  0xb6f9ace8 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 1 (Thread -1220041024 (LWP 32409)):
#0  0xb7fc4410 in ?? ()
#1  0xbfff73cc in ?? ()
#2  0x0011 in ?? ()
#3  0x in ?? ()
[END]

strace -p :

futex(0xaaca208, FUTEX_WAIT, 17, NULL unfinished ...

Could you propose any guesses ?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2007-01-16 Thread Mike Hommey
On Tue, Jan 16, 2007 at 08:45:16PM +0200, Wladimir Mutel [EMAIL PROTECTED] 
wrote:
   Hi,
 
   Same symptoms with iceape 1.0.7-2
   LD_ASSUME_KERNEL=2.4.1 does not help
   Being run with -debug option, iceape works more stable, in the
   sense that it hangs later. Without debugger, it hangs quite
   soon. Right when mail-news-related modal dialog is shown
   (unknown/unverified/expired certificate, re-entry of mail server
   password, etc).
 
   Backtrace from gdb :
(...)
   strace -p :
 
 futex(0xaaca208, FUTEX_WAIT, 17, NULL unfinished ...
 
   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 ?

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2007-01-16 Thread Wladimir Mutel
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  0x0001 in ?? ()
#3  0x in ?? ()

Thread 31 (Thread -1291469904 (LWP 15524)):
#0  0xb7fbf410 in ?? ()
#1  0xb305abc8 in ?? ()
#2  0x0007 in ?? ()
#3  0x in ?? ()

Thread 30 (Thread -1281279056 (LWP 15523)):
#0  0xb7fbf410 in ?? ()
#1  0xb3a1336c in ?? ()
#2  0x25a5 in ?? ()
#3  0x in ?? ()

Thread 28 (Thread -1314915408 (LWP 15521)):
#0  0xb7fbf410 in ?? ()
#1  0xb19ff36c in ?? ()
#2  0x25e1 in ?? ()
#3  0x in ?? ()

Thread 22 (Thread -1305085008 (LWP 15384)):
#0  0xb7fbf410 in ?? ()
#1  0xb235ef68 in ?? ()
#2  0x0071 in ?? ()
#3  0x in ?? ()

Thread 4 (Thread -1225167952 (LWP 14026)):
#0  0xb7fbf410 in ?? ()
#1  0xb6f95ce8 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 2 (Thread -1256887376 (LWP 14028)):
#0  0xb7fbf410 in ?? ()
#1  0xb51563e8 in ?? ()
#2  0x001a305b in ?? ()
#3  0x in ?? ()

Thread 1 (Thread -1220061504 (LWP 14018)):
#0  0xb7fbf410 in ?? ()
#1  0xbfc1c81c in ?? ()
#2  0x0011 in ?? ()
#3  0x 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 ?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2007-01-16 Thread Mike Hommey
On Wed, Jan 17, 2007 at 12:25:10AM +0200, Wladimir Mutel [EMAIL PROTECTED] 
wrote:
 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) :

There are 2 strange things in your backtrace. First, you don't have any
symbol which makes it pretty useless. Second, I've never seen a backtrace
with thread numbers  9 on mozilla products.

What could be helpful, anyways, would be for you to lookup what the
addresses in your backtrace point to, by looking at /proc/$PID/maps.

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2006-12-20 Thread Wladimir Mutel
On Thu, Dec 14, 2006 at 08:46:26PM +0200, Wladimir Mutel wrote:

  It'd be more helpful with a back trace ;)

ran iceape -debug, and caught this backtrace on hang.
Not very different from former one, and not very helpful.

(gdb) thread apply all bt

Thread 32 (Thread -1299764304 (LWP 16671)):
#0  0xb7f29410 in ?? ()
#1  0xb2872058 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 31 (Thread -1322640464 (LWP 16670)):
#0  0xb7f29410 in ?? ()
#1  0xb12a1058 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 29 (Thread -1267983440 (LWP 1)):
#0  0xb7f29410 in ?? ()
#1  0xb46c136c in ?? ()
#2  0x000255d7 in ?? ()
#3  0x in ?? ()

Thread 27 (Thread -1276376144 (LWP 16664)):
#0  0xb7f29410 in ?? ()
#1  0xb3ebfd98 in ?? ()
#2  0x0009 in ?? ()
#3  0x in ?? ()

Thread 13 (Thread -1347818576 (LWP 15871)):
#0  0xb7f29410 in ?? ()
#1  0xafa9df68 in ?? ()
#2  0x007f in ?? ()
#3  0x in ?? ()

Thread 4 (Thread -1257530448 (LWP 15859)):
#0  0xb7f29410 in ?? ()
#1  0xb50b93e8 in ?? ()
#2  0x7a9f in ?? ()
#3  0x in ?? ()

Thread 2 (Thread -1225733200 (LWP 15855)):
#0  0xb7f29410 in ?? ()
#1  0xb6f0bce8 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 1 (Thread -1220671808 (LWP 15852)):
#0  0xb7f29410 in ?? ()
#1  0xbfbe921c in ?? ()
#2  0x0005 in ?? ()
#3  0x in ?? ()
(gdb) 

strace -p ... (after doing detach in gdb) :

futex(0x94f07c8, FUTEX_WAIT, 5, NULL

Strangely, nobody other reports on this.
May be I am alone with my configuration ?
May be nobody else uses AMD K7 (Duron 1800) ?
What else can I have wrong ?



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2006-12-14 Thread Mike Hommey
On Thu, Dec 14, 2006 at 08:46:26PM +0200, Wladimir Mutel [EMAIL PROTECTED] 
wrote:
   After several days, everything was impeccable, but today in the
   morning my system restarted due to mains power loss. After reboot,
   I started iceape again, but forgot to attach gdb to it. And so,
   now, in the evening, I have found iceape hung again. In hurry, I
   attached gdb to it, but it said it failed to read a valid object
   file image from memory, and was not very informative overall :

Did you install the iceape-dbg package ?

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2006-12-14 Thread Wladimir Mutel
On Thu, Dec 07, 2006 at 10:16:11PM +0100, Mike Hommey wrote:

  I have upgraded from Mozilla 1.7.13-0.3 to iceape 1.0.6.
  I run iceape with the profile left from earlier mozilla.
  And so, when I leave the running browser unattended for several
  hours (for a night, say), and if during that time it shows some
  dialog or message box (like, enter mail server password, or,
  expired certificate, or, domain mismatch in certificate), then
  when I come back to the browser (in the morning), I find it
  hung. I.e. I could not close any dialogs or windows, and they do
  not redraw themselves. I am able to kill the browser by HUP
  signal. I did not try to debug the running process, but this is
  reproducible pretty often. Every night, I'd say. This behaviour
  was not seen with Mozilla 1.7. Hope you'd be able to reproduce
  it. I will provide any debugging information on your request.

 It'd be more helpful with a back trace ;)

Once I attached to the running iceape-bin by gdb. It behaved very
stably. Except for a few SIGPIPEs on network send() somewhere
in SSL innards, which broke into gdb, but then I continued the
execution, and all worked well.

After several days, everything was impeccable, but today in the
morning my system restarted due to mains power loss. After reboot,
I started iceape again, but forgot to attach gdb to it. And so,
now, in the evening, I have found iceape hung again. In hurry, I
attached gdb to it, but it said it failed to read a valid object
file image from memory, and was not very informative overall :

(gdb) thread apply all bt

Thread 14 (Thread -1225348176 (LWP 6410)):
#0  0xb7f87410 in ?? ()
#1  0xb6f69ce8 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 13 (Thread -1257047120 (LWP 6414)):
#0  0xb7f87410 in ?? ()
#1  0xb512f3e8 in ?? ()
#2  0xc40d in ?? ()
#3  0x in ?? ()

Thread 12 (Thread -1265751120 (LWP 6976)):
#0  0xb7f87410 in ?? ()
#1  0xb48e1f68 in ?? ()
#2  0x00a9 in ?? ()
#3  0x in ?? ()

Thread 11 (Thread -1248654416 (LWP 7174)):
#0  0xb7f87410 in ?? ()
#1  0xb593036c in ?? ()
#2  0x000113b3 in ?? ()
#3  0x in ?? ()

Thread 10 (Thread -1282536528 (LWP 8080)):
#0  0xb7f87410 in ?? ()
#1  0xb38e036c in ?? ()
#2  0x0001092f in ?? ()
#3  0x in ?? ()

Thread 9 (Thread -1356145744 (LWP 8085)):
#0  0xb7f87410 in ?? ()
#1  0xaf2ad36c in ?? ()
#2  0x0001091d in ?? ()
#3  0x in ?? ()

Thread 8 (Thread -1295230032 (LWP 8197)):
#0  0xb7f87410 in ?? ()
#1  0xb2cc536c in ?? ()
#2  0x000104ff in ?? ()
#3  0x in ?? ()

Thread 7 (Thread -1347753040 (LWP 8200)):
#0  0xb7f87410 in ?? ()
#1  0xafaae36c in ?? ()
#2  0x00010439 in ?? ()
#3  0x in ?? ()

Thread 6 (Thread -1322542160 (LWP 8202)):
#0  0xb7f87410 in ?? ()
#1  0xb12b936c in ?? ()
#2  0x0001042f in ?? ()
#3  0x in ?? ()

Thread 5 (Thread -1364538448 (LWP 8228)):
#0  0xb7f87410 in ?? ()
#1  0xaeaac36c in ?? ()
#2  0xfdb3 in ?? ()
#3  0x in ?? ()

Thread 4 (Thread -1339360336 (LWP 8229)):
#0  0xb7f87410 in ?? ()
#1  0xb02af36c in ?? ()
#2  0xfdb3 in ?? ()
#3  0x in ?? ()

Thread 3 (Thread -1372931152 (LWP 8235)):
#0  0xb7f87410 in ?? ()
#1  0xae2ab058 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 2 (Thread -1381323856 (LWP 8236)):
#0  0xb7f87410 in ?? ()
#1  0xadaaa058 in ?? ()
#2  0x0001 in ?? ()
#3  0x in ?? ()

Thread 1 (Thread -1220286784 (LWP 6404)):
#0  0xb7f87410 in ?? ()
#1  0xbff2a63c in ?? ()
#2  0x0011 in ?? ()
#3  0x in ?? ()
(gdb)


strace -p 6404 showed that the process is blocked on futex
syscall :

futex(0x9c85a88, FUTEX_WAIT, 17, NULL ...

Don't know what to do with these data next.

It seems iceape behaves dependently on whether it is ptraced or
not. Now I am restarting iceape and attaching gdb ot it in
advance, before it hangs, and let's see what will happen next.

Btw, there is program trafshow in package netdiag that hangs on
futex() as well. It seems to have something related to DNS
queries, but I did not explore the problem in depth.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2006-12-14 Thread Wladimir Mutel

Mike Hommey wrote:


After several days, everything was impeccable, but today in the
morning my system restarted due to mains power loss. After reboot,
I started iceape again, but forgot to attach gdb to it. And so,
now, in the evening, I have found iceape hung again. In hurry, I
attached gdb to it, but it said it failed to read a valid object
file image from memory, and was not very informative overall :



Did you install the iceape-dbg package ?


Yes. gdb reads a lot of debug info but then complains anyway, be
it freshly-started iceape, or hung one. Right now, the stacks
are as folllows :

(gdb) thread apply all bt

Thread 20 (Thread -1295483984 (LWP 10144)):
#0  0xb7f4f410 in ?? ()
#1  0xb2c8736c in ?? ()
#2  0x00e5 in ?? ()
#3  0x in ?? ()

Thread 17 (Thread -1278698576 (LWP 10094)):
#0  0xb7f4f410 in ?? ()
#1  0xb3c8936c in ?? ()
#2  0x06f9 in ?? ()
#3  0x in ?? ()

Thread 16 (Thread -1325446224 (LWP 10090)):
#0  0xb7f4f410 in ?? ()
#1  0xb0ff436c in ?? ()
#2  0x0729 in ?? ()
#3  0x in ?? ()

Thread 14 (Thread -1308660816 (LWP 10082)):
#0  0xb7f4f410 in ?? ()
#1  0xb1ff636c in ?? ()
#2  0x0749 in ?? ()
#3  0x in ?? ()

Thread 4 (Thread -1225577552 (LWP 10063)):
#0  0xb7f4f410 in ?? ()
#1  0xb6f32148 in ?? ()
#2  0x03e7fc18 in ?? ()
#3  0x0005 in ?? ()
#4  0xb75c8783 in poll () from /lib/tls/i686/cmov/libc.so.6
#5  0xb7df1ad9 in PR_Poll (pds=0x812a088, npds=5, timeout=65535000) at 
ptio.c:3877
#6  0xb6f6b76a in nsSocketTransportService::Poll (this=0x8129ba0, 
interval=0xb6f32408) at nsSocketTransportService2.cpp:359
#7  0xb6f6bf52 in nsSocketTransportService::Run (this=0x8129ba0) at 
nsSocketTransportService2.cpp:568

#8  0xb7f15dfb in nsThread::Main (arg=0x813eeb8) at nsThread.cpp:118
#9  0xb7df5cfc in _pt_root (arg=0x813ef38) at ptthread.c:220
#10 0xb7db1240 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb75d232e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread -1257489488 (LWP 10065)):
#0  0xb7f4f410 in ?? ()
#1  0xb50c33ac in ?? ()
#2  0x00016683 in ?? ()
#3  0x in ?? ()

Thread 1 (Thread -1220516160 (LWP 10057)):
#0  0xb7f4f410 in ?? ()
#1  0xbfe813f8 in ?? ()
#2  0x in ?? ()
#3  0x0007 in ?? ()
#4  0xb75c8783 in poll () from /lib/tls/i686/cmov/libc.so.6
#5  0xb777c7d9 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#6  0xb777cb67 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#7  0xb7be7281 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#8  0xb5a36152 in nsAppShell::Run (this=0x817ea90) at nsAppShell.cpp:139
#9  0xb60e7c84 in nsAppStartup::Run (this=0x816b110) at nsAppStartup.cpp:207
#10 0x0804bf87 in main1 (argc=3, argv=0xbfe81a64, nativeApp=value 
optimized out) at nsAppRunner.cpp:1249

#11 0x0804cffd in main (argc=Cannot access memory at address 0x7
) at nsAppRunner.cpp:1736
#12 0xb751bea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#13 0x0804a061 in _start () at ../sysdeps/i386/elf/start.S:119
(gdb)



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2006-12-07 Thread Wladimir Mutel
Package: iceape
Version: 1.0.6-1
Severity: important


Hi,

I have upgraded from Mozilla 1.7.13-0.3 to iceape 1.0.6.
I run iceape with the profile left from earlier mozilla.
And so, when I leave the running browser unattended for several
hours (for a night, say), and if during that time it shows some
dialog or message box (like, enter mail server password, or,
expired certificate, or, domain mismatch in certificate), then
when I come back to the browser (in the morning), I find it
hung. I.e. I could not close any dialogs or windows, and they do
not redraw themselves. I am able to kill the browser by HUP
signal. I did not try to debug the running process, but this is
reproducible pretty often. Every night, I'd say. This behaviour
was not seen with Mozilla 1.7. Hope you'd be able to reproduce
it. I will provide any debugging information on your request.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-k7
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8)

Versions of packages iceape depends on:
ii  iceape-browser1.0.6-1The Iceape Internet browser
ii  iceape-mailnews   1.0.6-1The iceape Internet application su

Versions of packages iceape recommends:
ii  iceape-chatzilla  1.0.6-1iceape Web Browser - irc client

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401995: iceape: hangs on modal dialogs and message boxes

2006-12-07 Thread Mike Hommey
On Thu, Dec 07, 2006 at 12:36:04PM +0200, Wladimir Mutel [EMAIL PROTECTED] 
wrote:
 Package: iceape
 Version: 1.0.6-1
 Severity: important
 
 
   Hi,
 
   I have upgraded from Mozilla 1.7.13-0.3 to iceape 1.0.6.
   I run iceape with the profile left from earlier mozilla.
   And so, when I leave the running browser unattended for several
   hours (for a night, say), and if during that time it shows some
   dialog or message box (like, enter mail server password, or,
   expired certificate, or, domain mismatch in certificate), then
   when I come back to the browser (in the morning), I find it
   hung. I.e. I could not close any dialogs or windows, and they do
   not redraw themselves. I am able to kill the browser by HUP
   signal. I did not try to debug the running process, but this is
   reproducible pretty often. Every night, I'd say. This behaviour
   was not seen with Mozilla 1.7. Hope you'd be able to reproduce
   it. I will provide any debugging information on your request.

It'd be more helpful with a back trace ;)

Cheers,

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]