253556 - Curious Character in News, and Mozilla freezes with large CPU load

Status: RESOLVED EXPIRED

(MailNews Core :: Backend, defect)

Description

[Volker Moell]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040728 Mnenhy/0.6.0.100
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040728 Mnenhy/0.6.0.100

My Mozilla freezes today when opening the newsgroup
de.comm.software.mozilla.nightly-builds. The problem was the posting
<[e-mail]>. It contains a curious sign in the
subject.  Someone said this sign is "\uFFFC = OBJECT REPLACEMENT CHARACTER".

When this sign only is in the body (not in subject) Mozilla freezes when opening
the posting, not when entering the newsgroup.


Reproducible: Always
Steps to Reproduce:
1. Open Mozilla Mail/News
2. Subscribe to de.comm.software.mozilla.nightly-builds and fetch Portings at
least from 2004-07-29
3. Mozilla freezes.

1. Open Mozilla Mail/News
2. Subscribe to de.comm.software.mozilla.nightly-builds and fetch Portings at
least from 2004-07-29
3. Open <[e-mail]> (e.g. via MIDF)
4. Mozilla freezes. 

Actual Results:  
Mozilla freezes and must be killed ("kill mozilla-bin" with no special signal).

Expected Results:  
Show the posting instead and do not freeze.

I tried several older CVS Mozilla releases, from 2004-05-29 to 2004-07-28. Each
one has this problem.
Other people in the newsgroup do *not* have this problem.

Comment 1

[Daniel Küstner]

Did you try a virgin profile?

Comment 2

[Volker Moell]

Yes, with a completely missing ~/.mozilla.  Same effect.

Comment 3

[Tuukka Tolvanen (sp3000)]

the comments on bug 250718 might have clues

Comment 4

[Volker Moell]

Maybe it helps when printing my about:buildconfig.  Here it is

Build platform
target
i686-pc-linux-gnu

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

Configure arguments
--prefix=/opt --disable-debug --enable-optimize --disable-tests
--disable-pedantic --without-system-nspr --without-system-zlib
--without-system-jpeg --without-system-png --without-system-mng --enable-mathml
--disable-xft --enable-freetype2 --enable-crypto --enable-strip
--enable-calendar --enable-xterm-updates --disable-ldap --disable-auto-deps

My Linux system is based on a SUSE-9.1, but with several self-built RPMs.

(BTW: The kill command when mozilla freezes of course is "killall mozilla-bin"
instead of "kill mozilla-bin")

Comment 5

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

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.