Closed
Bug 913814
Opened 11 years ago
Closed 11 years ago
HTTP cache v2: check why test_304_responses.js is slow
Categories
(Core :: Networking: Cache, defect)
Core
Networking: Cache
Tracking
()
RESOLVED
FIXED
mozilla27
People
(Reporter: mayhemer, Assigned: mayhemer)
References
Details
(Whiteboard: [cache2])
Attachments
(1 file)
1.86 KB,
patch
|
michal
:
review+
mayhemer
:
checkin+
|
Details | Diff | Splinter Review |
seems like main thread is held for 5 seconds from some reason (maybe something with the MetadataWriteTimer::Notify)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → honzab.moz
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•11 years ago
|
||
- the problem was not at all with MetadataWriteTimer::Notify - many things are using 5 seconds in the platform :) - this time it was close of an idle connection (from the client side) that closed connection also on the server side that triggered GC that end up freeing the entry handle that ended up CacheEntry::OnWriterClosed that moved the test forward - just added metaDataReady() call to the right place (where it has to be with the new API) and it's done Thinking of whether Close on the new entry impl should call metaDataReady() or even setValid() to have better backward compat...
Attachment #803128 -
Flags: review?(michal.novotny)
Comment 2•11 years ago
|
||
Comment on attachment 803128 [details] [diff] [review] v1 (In reply to Honza Bambas (:mayhemer) from comment #1) > Thinking of whether Close on the new entry impl should call metaDataReady() > or even setValid() to have better backward compat... But we don't call Close() explicitly.
Attachment #803128 -
Flags: review?(michal.novotny) → review+
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Michal Novotny (:michal) from comment #2) > Comment on attachment 803128 [details] [diff] [review] > v1 > > (In reply to Honza Bambas (:mayhemer) from comment #1) > > Thinking of whether Close on the new entry impl should call metaDataReady() > > or even setValid() to have better backward compat... > > But we don't call Close() explicitly. Yeah, and close() will eventually be removed anyway. Probably not a good idea to do it. We will break add-ons compatibility anyway after bug 913828 lands and actually silently break it (by means of not giving the desired results in most cases) with bug 913806.
Assignee | ||
Comment 4•11 years ago
|
||
Comment on attachment 803128 [details] [diff] [review] v1 https://hg.mozilla.org/integration/mozilla-inbound/rev/5dd68636da74
Attachment #803128 -
Flags: checkin+
Comment 5•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/5dd68636da74
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
You need to log in
before you can comment on or make changes to this bug.
Description
•