Closed
Bug 817202
Opened 12 years ago
Closed 7 years ago
asyncOpen of jar:file:// does blocking I/O on main thread
Categories
(Core :: Networking: JAR, defect)
Core
Networking: JAR
Tracking
()
RESOLVED
DUPLICATE
of bug 1373708
People
(Reporter: jduell.mcbugs, Unassigned)
Details
(Keywords: main-thread-io, perf, Whiteboard: [necko-backlog])
CreateJarInput() winds up calling (via the zipcache) all the way down to nsZipHandle::Init(), which does OpenNSPRFileDesc() and PR_MemMap(). No particular reason this needs to block main thread AFAICT--we're already past the point in AsyncOpen where we're committed to returning NS_OK and returning errors via OnStopRequest.
Reporter | ||
Comment 1•12 years ago
|
||
CreateJarInput call: http://mxr.mozilla.org/mozilla-central/source/modules/libjar/nsJARChannel.cpp?rev=736e9f98d97a#711 and comment that says we're no longer returning errors synchronously: http://mxr.mozilla.org/mozilla-central/source/modules/libjar/nsJARChannel.cpp?rev=736e9f98d97a#692
Reporter | ||
Comment 2•12 years ago
|
||
Note that with jar caching this only happens once per jarfile in the common case, not per channel.
Comment 4•10 years ago
|
||
Well, main thread I/O is always bad. I believe that this is worth pursuing.
Keywords: main-thread-io
Updated•8 years ago
|
Whiteboard: [necko-backlog]
Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•