Closed
Bug 1694885
Opened 5 years ago
Closed 5 years ago
Migrate Omnijar.h from direct use of nsZipArchive to nsJar
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jstutte, Unassigned)
References
Details
Omnijar.h is not thread-safe by design, but we access omnijar from different threads.
|
||
Updated•5 years ago
|
Severity: -- → S3
Priority: -- → P3
|
Reporter | |
Updated•5 years ago
|
Component: DOM: Core & HTML → XPCOM
Summary: Migrate nsHyphenationManager from direct use of nsZipArchive to nsJar → Migrate Omnijar.h from direct use of nsZipArchive to nsJar
|
||
Comment 1•5 years ago
|
||
The component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.
Priority: P3 → --
|
||
Comment 2•5 years ago
|
||
See bug 1656329 comment #8.
I think making nsZipArchive thread-safe should be enough.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•