Open
Bug 309562
Opened 19 years ago
Updated 2 years ago
nsLocalFile::CopySingleFile backup names need unique-ifying
Categories
(Core :: XPCOM, defect)
Tracking
()
NEW
People
(Reporter: dmosedale, Unassigned)
References
()
Details
(Keywords: helpwanted)
I just killed a bunch of hours tracking down a bug to code with the following comment (see the URL field): // remove any existing backup file that we may already have. // maybe we should be doing some kind of unique naming here, // but why bother. The answer to this (obviously rhetorical) question is this: if code calls nsILocalFile::MoveTo() twice in (not particularly rapid) succession to rotate backup files, then somebody (the kernel?) can still be holding on to the first backup when the second backup attempt tries to remove it. This means that the remove (and therefore the subsequent MoveFile) fails, causing the entire MoveTo to croak with the extremely unhelpful NS_ERROR_FAILURE.
Updated•19 years ago
|
Flags: blocking1.9a1?
Keywords: helpwanted
Updated•18 years ago
|
Flags: blocking1.9a1? → blocking1.9-
Whiteboard: [wanted-1.9]
Updated•17 years ago
|
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•