Closed Bug 742218 Opened 8 years ago Closed 4 years ago

Make nsHttpChannel's use of nsApplicationCache/nsIApplicationCache thread-safe

Categories

(Core :: Networking: Cache, defect)

defect
Not set

Tracking

()

RESOLVED WONTFIX

People

(Reporter: briansmith, Unassigned)

Details

This looks like it would require:

1. Make GetMatchingNamespace callable off the main thread, or rewrite nsHttpChannel to avoid calling it after AsyncOpen.

2. Maybe make GetClientID and GetTypes thread-safe, or rewrite nsHttpChannel to avoid calling them after AsyncOpen.

3. If necessary, implement thread-safe AddRef/Release for nsApplicationCache, and make nsIApplicationCache [builtinclass] since it would not be possible to implement it in JS.
(In reply to Brian Smith (:bsmith) from comment #0)
> This looks like it would require:
> 
> 1. Make GetMatchingNamespace callable off the main thread, or rewrite
> nsHttpChannel to avoid calling it after AsyncOpen.

Note: this performs an sqlite query.
No longer blocks: 722034
app cache on the way out..
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.