STR:
1. Go to http://www.procata.com/cachetest/
2. Click on the Expires "Perform Test" link
3. Click on the "Click here to go to step 2" link
4. Go Offline
5. Click on the "Click here to go to step 3" link (loads the same page as [2], but to pass it must not load the cached version).
6. Hover the "Click here to complete the test" and note it is "fail.html"
In [6], if we weren't loading an expired entry, we would get the Offline error page. If we were online, it would replace the page with one where the link is to "pass.html"
Unless I'm misunderstanding the test, we're still getting expired entries (either without |LOAD_ONLY_FROM_CACHE|, or it's set later).
I'm also seeing warnings about potential deadlock again. Is this just a conservative warning, or something to be addressed?
Output:
> ###!!! ASSERTION: Potential deadlock detected:
> Cyclical dependency starts at
> ReentrantMonitor : nsHttpConnectionMgr.mReentrantMonitor
> Next dependency:
> Mutex : nsSocketTransportService::mLock (currently acquired)
> Cycle completed at
> ReentrantMonitor : nsHttpConnectionMgr.mReentrantMonitor
> Deadlock may happen for some other execution
Created attachment 655837
Unbitrot and prepare for checkin
FWIW I tried the 'expires' test on http:// www.procata. com/cachetest/ using the patch.
STR: www.procata. com/cachetest/
1. Go to http://
2. Click on the Expires "Perform Test" link
3. Click on the "Click here to go to step 2" link
4. Go Offline
5. Click on the "Click here to go to step 3" link (loads the same page as [2], but to pass it must not load the cached version).
6. Hover the "Click here to complete the test" and note it is "fail.html"
In [6], if we weren't loading an expired entry, we would get the Offline error page. If we were online, it would replace the page with one where the link is to "pass.html"
Unless I'm misunderstanding the test, we're still getting expired entries (either without |LOAD_ONLY_ FROM_CACHE| , or it's set later).
I'm also seeing warnings about potential deadlock again. Is this just a conservative warning, or something to be addressed?
Output:
> ###!!! ASSERTION: Potential deadlock detected: nMgr.mReentrant Monitor rtService: :mLock (currently acquired) nMgr.mReentrant Monitor
> Cyclical dependency starts at
> ReentrantMonitor : nsHttpConnectio
> Next dependency:
> Mutex : nsSocketTranspo
> Cycle completed at
> ReentrantMonitor : nsHttpConnectio
> Deadlock may happen for some other execution
Pushed to try: /tbpl.mozilla. org/?tree= Try&rev= 7d24d71d64b2
https:/