hang when opening a directory for an attachment when that directory contains a very long file name with an non ascii character ó



Core Graveyard
File Handling
14 years ago
2 years ago


(Reporter: James Dow, Unassigned)


Firefox Tracking Flags

(Not tracked)




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

I am not sure whether or not it was the length of the file name which contained
around twenty words separated by blanks or it was the non-ascii character ó that
caused the file browser in mozilla to hang the program. The directory was not
opened and mozilla stopped. On investigation of the pecularity of that
directory, the long file name with the non-ascii character was discovered. The
non-ascii character was removed, and the file name was shortened. Then, mozilla
could open the directory.

Reproducible: Always

Steps to Reproduce:
1. Put a long-named file with blanks and non-ascii characters in the name in a
2. Try to open that directory to find a mail attachment.

Expected Results:  
It should have opened the directory.
Note that this bug was reported automatically by Bugzilla, but the cause was
discovered later.
what's your locale? (LANG environment variable, or LC_CTYPE if set)

also, could you try mozilla 1.6? iirc that bug was fixed in that version by
jshin or bz
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/
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
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.