Status Update
No update yet.
Comments
va...@chromium.org
[Empty comment from Monorail migration]
mm...@chromium.org
We aren't actually waiting on the cache. Looks like we're waiting on the SSLManager to do something (While the request is blocked on URL_REQUEST_DELEGATE_SSL_CERTIFICATE_ERROR). The fact that we blame this on the cache is perhaps also worth fixing.
[Monorail components: -Internals>Network Internals>Network>SSL]
[Monorail components: -Internals>Network Internals>Network>SSL]
da...@chromium.org
It is actually waiting on the cache. The first request is blocked on URL_REQUEST_DELEGATE_SSL_CERTIFICATE_ERROR but the other is blocked on HTTP_CACHE_ADD_TO_ENTRY by way of the cache lock.
The committed interstitials work (I think it's issue #448486?) should fix this.
The committed interstitials work (I think it's issue #448486?) should fix this.
is...@google.com
This issue was migrated from crbug.com/chromium/863935?no_tracker_redirect=1
[Monorail mergedinto:crbug.com/chromium/6697 ]
[Monorail components added to Component Tags custom field.]
[Monorail mergedinto:
[Monorail components added to Component Tags custom field.]
Description
Example URL:
Steps to reproduce the problem:
1. Visit
2. Open a second tab to
3. Observe "Waiting for cache..." in the status bar for 15 seconds before the second tab loads
What is the expected behavior?
Cache is not blocked on another tab's Privacy error page
What went wrong?
Chrome is blocked on the cache for 15 seconds
Did this work before? N/A
Chrome version: 69.0.3486.0 Channel: stable
OS Version: Debian 9.5
Flash Version:
This is pretty confusing when you've forgotten about the tab on the Privacy error page.
This also happens with other SSL errors linked from
This happens even if the SSL error is now fixed, but the Privacy error tab is still open.