Your message dated Tue, 1 May 2007 09:03:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#226358: Mozilla-printing: When I try to print on my amd-k6 
mozilla locks up.
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: mozilla
Version: 2:1.5-3
Severity: normal

Any page I try and print I have to kill mozilla.  The preparing job window
and the main mozilla window don't refresh.  mozilla.bin takes 100% cpu and I
can kill it via a normal kill.  I have let mozilla sit for several hours,
but it never finneshes.

I have an AMD-k6 and mozilla dose work fine on all my other computers.

I realy do HATE it when gcc makes asm like this.  Whatever can loop will loop.
0x080714f0 <_ZN12nsStrPrivate12GrowCapacityER5nsStrj+112>:      add    %eax,%eax
0x080714f2 <_ZN12nsStrPrivate12GrowCapacityER5nsStrj+114>:      cmp    %esi,%eax
0x080714f4 <_ZN12nsStrPrivate12GrowCapacityER5nsStrj+116>:      jb     0x80714f0

Here is a regdump.
eax            0x0      0
ecx            0x0      0
edx            0x807e690        134735504
ebx            0x80809b4        134744500
esp            0xbfffd104       0xbfffd104
ebp            0xbfffd14c       0xbfffd14c
esi            0xffffffff       -1
edi            0xbfffd3d8       -1073753128
eip            0x80714f0        0x80714f0
eflags         0x200313 2097939
cs             0x73     115
ss             0x7b     123
ds             0x7b     123
es             0x7b     123
fs             0x0      0
gs             0x33     51

Here is a backtrace.
#0  0x080714f0 in nsStrPrivate::GrowCapacity(nsStr&, unsigned) ()
#1  0x08069b1c in nsCString::SetCapacity(unsigned) ()
#2  0x08069aa4 in nsCString::SetLength(unsigned) ()
#3  0x0805e897 in nsACString::UncheckedAppendFromReadable(nsACString const&) ()
#4  0x0805e6ac in nsACString::do_AppendFromReadable(nsACString const&) ()
#5  0x440e091e in ?? () from /usr/lib/mozilla/components/libgfxps.so
#6  0xbfffd3d4 in ?? ()
#7  0xbfffd334 in ?? ()

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux filbert 2.6.0-test9-1-386 #1 Sun Oct 26 22:32:52 EST 2003 i586
Locale: LANG=C, LC_CTYPE=C

Versions of packages mozilla depends on:
ii  dpkg                          1.10.18    Package maintenance system for Deb
ii  mozilla-browser               2:1.5-3    Mozilla Web Browser - core and bro
ii  mozilla-mailnews              2:1.5-3    Mozilla Web Browser - mail and new
ii  mozilla-psm                   2:1.5-3    Mozilla Web Browser - Personal Sec
ii  mozilla-xft                   2:1.5-3    Mozilla Web Browser - Xft support 

-- no debconf information



--- End Message ---
--- Begin Message ---
On Tue, Jan 06, 2004 at 12:28:43AM -0600, Mike Mestnik) (the Archmage forever 
<[EMAIL PROTECTED]> wrote:
> Package: mozilla
> Version: 2:1.5-3
> Severity: normal
> 
> Any page I try and print I have to kill mozilla.  The preparing job window
> and the main mozilla window don't refresh.  mozilla.bin takes 100% cpu and I
> can kill it via a normal kill.  I have let mozilla sit for several hours,
> but it never finneshes.
> 
> I have an AMD-k6 and mozilla dose work fine on all my other computers.
> 
> I realy do HATE it when gcc makes asm like this.  Whatever can loop will loop.
> 0x080714f0 <_ZN12nsStrPrivate12GrowCapacityER5nsStrj+112>:      add    
> %eax,%eax
> 0x080714f2 <_ZN12nsStrPrivate12GrowCapacityER5nsStrj+114>:      cmp    
> %esi,%eax
> 0x080714f4 <_ZN12nsStrPrivate12GrowCapacityER5nsStrj+116>:      jb     
> 0x80714f0
(...)

Considering this bug is 3 years old, didn't get reported against
iceape (which replaces mozilla nowadays) yet, and provided nsStrPrivate
doesn't exist anymore, I think we are safe closing this bug now.

However, if you happen to still have this problem, please feel free to
either reopen the bug or file a new one

Thanks

Mike


--- End Message ---

Reply via email to