Mozilla stops responding; UI "smears" when moved



15 years ago
13 years ago


(Reporter: hcaley, Unassigned)



Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030914
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030914

Mozilla stops responding; any Mozilla Windows I have open stop accepting input,
and they "smear" if I move them around behind other windows or widgets, etc.

I can killall mozilla-bin, and restart, but eventually it will lock up again

Reproducible: Sometimes

Steps to Reproduce:

I'm using RedHat 9, with all updates available as of 9/12/2003.  I've seen it
happen on Mozilla 1.2 (redhat's shipped version), 1.4 and the latest trunk
builds for i686 Linux.


15 years ago
Keywords: hang
Which exact builds are you using?  The tarballs or the RPM builds?

Comment 2

15 years ago
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030914
mozilla-1.2.1-26 rpms

Trunk seems to go down more easily, but it's happened with 1.4 and 1.2.1 as well.
Are those first two tarballs or RPM builds?  What does about:buildconfig say?

Comment 4

15 years ago
They are both tarballs from  One is the released version of 1.4 for
Linux; the other is a trunk build from 8/14; about:buildconfig below:

Build platform

Build tools
Compiler 	Version 	Compiler flags
gcc 	gcc version 3.2.3 	-Wall -W -Wno-unused -Wpointer-arith -Wcast-align
-Wno-long-long -pedantic -g -pthread -pipe
c++ 	gcc version 3.2.3 	-fno-rtti -fno-exceptions -Wall -Wconversion
-Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy
-Wno-long-long -pedantic -g -fshort-wchar -pthread -pipe -I/usr/X11R6/include

Configure arguments
--disable-tests --enable-extensions=default,irc --without-system-nspr
--without-system-jpeg --without-system-zlib --without-system-png
--without-system-mng --disable-debug --enable-optimize --disable-elf-dynstr-gc
--enable-optimize=-O2 --enable-crypto 
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.