Closed
Bug 94010
Opened 24 years ago
Closed 23 years ago
Insufficient free space causes loss of preferences
Categories
(Core :: Preferences: Backend, defect)
Core
Preferences: Backend
Tracking
()
mozilla1.0
People
(Reporter: olgac, Assigned: bnesse)
References
Details
(Keywords: dataloss)
In situation when we are running low on free space
rewriting prefs.js file leads to corruption of the file (it gets truncated) or
total loss of preferences (we get 0KB prefs.js).
Safer way to do it would be to move prefs.js to backup file before creating new
prefs.js or save the new copy of the prefs to a temporary file in the same
directory as prefs.js. If creation of the new file is successful, then rid of
the old file.
Comment 1•24 years ago
|
||
Am I wrong or is this a dupe of #86501 where exactly this behaviour and solution
are described? If then I suggest closing this to get rid of an open bug :)
![]() |
Assignee | |
Comment 2•24 years ago
|
||
Not that I'm against dupes :) but bug 86501 references multiple files which are
corrupted in this situation. If there were some sort of "safe save" convention
in Mozilla, it could potentially be fixed via one bug. If this exists, I'm not
aware of it. Since the files in question cross multiple components (bookmarks,
for example, is Ben's area) I would leave them both open as the work will
probably have to be done per component.
![]() |
Assignee | |
Updated•24 years ago
|
Target Milestone: --- → mozilla0.9.9
Updated•24 years ago
|
Blocks: profile-corrupt
![]() |
Assignee | |
Comment 4•24 years ago
|
||
This was fixed by the checkin for bug 98476.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
![]() |
Assignee | |
Comment 6•24 years ago
|
||
Re opening as per previous comment.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
![]() |
Assignee | |
Updated•24 years ago
|
Target Milestone: mozilla0.9.9 → mozilla1.0
![]() |
||
Comment 8•24 years ago
|
||
*** Bug 129579 has been marked as a duplicate of this bug. ***
Comment 9•23 years ago
|
||
Updated•23 years ago
|
No longer blocks: profile-corrupt
Comment 11•22 years ago
|
||
*** Bug 142222 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•