Closed
Bug 1659239
Opened 4 years ago
Closed 3 years ago
NS_ERROR_FILE_UNRECOGNIZED_PATH in L10nRegistry.jsm after clearing startup cache
Categories
(Core :: Internationalization, defect, P3)
Core
Internationalization
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox92 | --- | fixed |
People
(Reporter: flod, Unassigned)
References
Details
Noticed while trying to figure out another bug
Open about:support, clear the start-up cache and restart. After the restart, the console will report 3 errors of the same type
[Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]" nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 684" data: no] L10nRegistry.jsm:684:19
loadSync resource://gre/modules/L10nRegistry.jsm:684
fetchFile resource://gre/modules/L10nRegistry.jsm:599
generateResourceSetSync resource://gre/modules/L10nRegistry.jsm:504
map self-hosted:221
generateResourceSetSync resource://gre/modules/L10nRegistry.jsm:499
generateResourceSetsForLocaleSync resource://gre/modules/L10nRegistry.jsm:441
next self-hosted:1416
generateResourceSetsForLocaleSync resource://gre/modules/L10nRegistry.jsm:450
next self-hosted:1416
generateResourceSetsForLocaleSync resource://gre/modules/L10nRegistry.jsm:450
next self-hosted:1416
generateResourceSetsForLocaleSync resource://gre/modules/L10nRegistry.jsm:450
InterpretGeneratorResume self-hosted:1468
next self-hosted:1416
generateResourceSetsForLocaleSync resource://gre/modules/L10nRegistry.jsm:450
InterpretGeneratorResume self-hosted:1468
next self-hosted:1416
generateBundlesSync resource://gre/modules/L10nRegistry.jsm:178
InterpretGeneratorResume self-hosted:1468
next self-hosted:1416
next resource://gre/modules/Localization.jsm:147
formatWithFallbackSync resource://gre/modules/Localization.jsm:287
formatMessagesSync resource://gre/modules/Localization.jsm:354
Restart normally and there won't be any errors. I guess the lack of cache is not correctly managed, then it creates it and everything works as normal?
Comment 1•4 years ago
|
||
The severity field is not set for this bug.
:m_kato, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(m_kato)
Updated•4 years ago
|
Severity: -- → S3
Flags: needinfo?(m_kato)
Priority: -- → P3
Comment 3•3 years ago
|
||
L10nRegistry.jsm has been removed in bug 1660392.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Comment hidden (off-topic) |
Comment hidden (off-topic) |
Updated•3 years ago
|
status-firefox92:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•