Closed Bug 176943 Opened 23 years ago Closed 2 years ago

Mozilla unaware of windows path length limit

Categories

(Firefox :: File Handling, defect)

x86
Windows NT
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: mfedyk, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826 Windows has a problem with files and directories with a path larger than 250 chars, and mozilla is unaware of that. Mozilla will also happily move a mail folder below another folder, and then won't be able to access the emails in the moved folder afterwards. If you don't know how to rename the folders while mozilla is closed, you will lose (though not permanently), any folders that hit this limit. Reproducible: Always Steps to Reproduce: 1. Create a bunch of folders with long names (no longer than 55 chars.) with one or more messages in each folder. 2. Nest b below a, and so on until you do so anymore ie, a-> b -> c -> d, etc. At a certain point it will fail, and you won't be able to nest anymore. 1. Create new folders with long names (55 chars per folder name max) until the windows path is longer than 250 chars EX: C:\WINNT\Profiles\jackief\Application Data\Mozilla\Profiles\default\rxpj13m0.slt\Mail\mail\11111111111111111111111111111111111111111111111111a.sbd\11111111111111111111111111111111111111111111111111b.sbd\111111111111111111111111111111111111122222 2. try to copy messages into the long nested folder, you shouldn't be ablt to, and you can't rename it either. 3. Actual Results: You can't access/move/rename the copied/renamed/created folder anymore. If you try to read it, it will just sit there listing the previous folders contents (if you were in inbox, it will still show the listing from inbox even though you clicked on the inaccessable folder because the message list isn't updated) Expected Results: Fail to move/rename/create folders that will hit the windows path length limit. -and/or- Keep track of the cwd, and use relative paths instead of the full path of the folder. This might have relevance to bugs 126647, and 147528.
QA Contact: gayatri → laurel
-> Navin
Assignee: mscott → naving
Status: UNCONFIRMED → NEW
Ever confirmed: true
One way to fix it would be to reduce MAX_LEN say to 20, that would allow sufficient children within path limit of 250 chars. #elif defined(XP_WIN32) const PRUint32 MAX_LEN = 55;
I have folder names longer than 20 characters - I think we should enforce the actual limit, which is the length of the whole file path, and have better error checking/handling.
Depends on: 176948
Flags: blocking1.3a?
Flags: blocking1.3a? → blocking1.3a-
mass re-assign.
Assignee: naving → sspitzer
Product: MailNews → Core
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Filter on "Nobody_NScomTLD_20080620"
QA Contact: laurel → backend
Product: Core → MailNews Core
Component: Backend → File Handling
Product: MailNews Core → Core
(In reply to Mike Fedyk from comment #0) > This might have relevance to bugs 126647, and 147528. Linkify for ease of access to other bugs. This might have relevance to Bug 126647, and Bug 147528.
See Also: → 1093035
Product: Core → Firefox
Version: Trunk → unspecified

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: critical → --

The severity field is not set for this bug.
:Gijs, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(gijskruitbosch+bugs)

This isn't a valid Firefox bug and any remaining issues exist in Thunderbird they should be filed there (as, it seems, bug 1093035 already was).

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(gijskruitbosch+bugs)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.