279475 - Non printable characters crash Firefox

Status: RESOLVED EXPIRED

(Core :: Internationalization, defect)

Description

[riccardo caroli]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; it-IT; rv:1.7.5) Gecko/20041110 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; it-IT; rv:1.7.5) Gecko/20041110 Firefox/1.0

firefox crash when browsing in this page,
and sometimes also on google 

Reproducible: Sometimes

Steps to Reproduce:
1. http://www.markme.com/mxna/index.cfm?category=Flash
2.
3.

Actual Results:  
the browser freezes on windows xp sp1

Comment 1

[José Jeria]

WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050121
Firefox/1.0+

Comment 2

[Ian Graham]

WFM on 
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
I tried loading the pages several times, and all was fine. 

Comment 3

[Oliver Klee]

A freeze is a hang, not a crash.

Comment 4

[riccardo caroli]

Attachment: non system characters on explorer

see the attachment.
i've found what the freezes are caused. 

It seems that non-system characters that are not rendered by the browser
crashes firefox (explorer renders them with a empty cube).

http://forum.mamboserver.com/showthread.php?t=4570

Also Mozilla Thunderbird seems to have the same bug, cause today crashed when
trying to read a email from a 

mailing-list where the subject was talking about japanese characters

Aw great i've found a big bug, who will find the fix now? :)

thanks

Comment 5

[Frank Wein [:mcsmurf]]

That characters (for example under
http://casario.blogs.com/mmworld/2005/01/new_peldis_codi.html) seem to be UTF-8.
But when i switch to ISO-8859-1 under win2k, i still get something (strange
characters, but not those empty cubes).

Comment 6

[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 7

[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.