Open
Bug 296177
Opened 20 years ago
Updated 2 years ago
ERROR path that can happen in readonly envs should not use NS_ERROR
Categories
(Core :: XPCOM, defect)
Tracking
()
NEW
People
(Reporter: timeless, Unassigned)
References
()
Details
(Keywords: assertion)
I happened to hit this because my components directory was a junction which one of my computers didn't handle, but it should be possible to simply setup a box where there is no current/happy xpti.dat and where the directory/file is readonly. this should not be an error case.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•