CHECK fail when launch vr.with.in directly from the "enter VR" button |
||||
Issue descriptionChrome Version: TOT today What steps will reproduce the problem? (1)navigate to vr.with.in (2)press enter vr button (3)pair controller What is the expected result? See vr version of the website What happens instead? After pairing, there is a chrome crash and we go back to controller paired screen and stucked at here. The crash was due to this I think: [FATAL:dom_storage_area.cc(312)] Check failed: !session_storage_backing_.get(). Stack Trace: RELADDR FUNCTION FILE:LINE 000a7c59 logging::LogMessage::~LogMessage() /usr/local/google/home/bshe/projects/cr/src/base/logging.cc:553 007eef0f content::DOMStorageArea::PurgeMemory() /usr/local/google/home/bshe/projects/cr/src/content/browser/dom_storage/dom_storage_area.cc:312 007f73d3 content::DOMStorageNamespace::PurgeMemory(bool) /usr/local/google/home/bshe/projects/cr/src/content/browser/dom_storage/dom_storage_namespace.cc:150 007f10a9 content::DOMStorageContextImpl::PurgeMemory(content::DOMStorageContextImpl::PurgeOption) /usr/local/google/home/bshe/projects/cr/src/content/browser/dom_storage/dom_storage_context_impl.cc:523
,
Jul 11 2017
Is this perhaps similar to issue 727955 where we call back into something we suppressed and/or related to issue 728421 .
,
Jul 12 2017
If this is consistent, it should be easy to bisect.
,
Jul 13 2017
No longer reproducible on today's TOT or canary
,
Jul 4
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ddorwin@chromium.org
, Jul 11 2017Status: Available (was: Untriaged)