IsInTreeScope DCHECK failure in blink::Node::ContainingTreeScope() |
|||||||||||
Issue descriptionChrome Version: r475616 OS: Linux What steps will reproduce the problem? (1) In a developer build, visit chrome://gpu (2) In the "Problems Detected" section, right click on some italicized text and select "Inspect" What is the expected result? Devtools opens up to the element I want to inspect. What happens instead? I get a DCHECK failure: [1:1:0530/191302.444994:FATAL:Node.h(575)] Check failed: IsInTreeScope(). #0 0x7f1cad556aab base::debug::StackTrace::StackTrace() #1 0x7f1cad5557ac base::debug::StackTrace::StackTrace() #2 0x7f1cad5c9353 logging::LogMessage::~LogMessage() #3 0x7f1c9b58de26 blink::Node::ContainingTreeScope() #4 0x7f1c9b58a19c blink::RulesApplicableInCurrentTreeScope() #5 0x7f1c9b589eb6 blink::ElementRuleCollector::CollectMatchingRules() #6 0x7f1c9b6bbea3 blink::ScopedStyleResolver::CollectMatchingAuthorRules() #7 0x7f1c9b6e2e12 blink::StyleResolver::MatchAuthorRulesV0() #8 0x7f1c9b6e2cb6 blink::StyleResolver::MatchAuthorRules() #9 0x7f1c9b6e746b blink::StyleResolver::CollectPseudoRulesForElement() #10 0x7f1c9b6e7627 blink::StyleResolver::PseudoCSSRulesForElement() #11 0x7f1c9bf93f2b blink::InspectorCSSAgent::getMatchedStylesForNode() #12 0x7f1c9bf95115 blink::InspectorCSSAgent::getMatchedStylesForNode() #13 0x7f1c9cca6edb blink::protocol::CSS::DispatcherImpl::getMatchedStylesForNode() #14 0x7f1c9cca69b6 blink::protocol::CSS::DispatcherImpl::dispatch() #15 0x7f1c9cd6e492 blink::protocol::UberDispatcher::dispatch() #16 0x7f1c9c05f012 blink::InspectorSession::DispatchProtocolMessage() #17 0x7f1c97eb2ac0 blink::WebDevToolsAgentImpl::DispatchMessageFromFrontend() #18 0x7f1c97eb294e blink::WebDevToolsAgentImpl::DispatchOnInspectorBackend() #19 0x7f1ca793bfa1 content::DevToolsAgent::OnDispatchOnInspectorBackend()
,
Jun 1 2017
,
Jun 1 2017
,
Jun 1 2017
Unable to reproduce the issue on 61.0.3118.0 (Developer Build) (64-bit) on Linux Ubuntu 14.04. Attached is the screen-cast of the same. Downloaded Chromium from https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/.
,
Jun 1 2017
Not able to reproduce this (neither with chromium nor content_shell built from master).
,
Jun 1 2017
ajha: I don't think the developer builds you downloaded have DCHECKs enabled. So those builds cannot be used to reproduce this bug. rune: If there's some extra logging that I can add or enable to help debug this, let me know. My git tree is now at r476201 and I can still reproduce this. Maybe my chrome://gpu has different contents that triggers this? (attached)
,
Jun 2 2017
Adding 'stability' label, as a DCHECK failure is usually indicative that code is entering an unspecified state.
,
Jun 2 2017
,
Jun 4 2017
Unlike rune, I was able to repro this on TOT Debug chrome build (version 61.0.3120.0) using my own chrome://gpu page (did not need to use the one attached by thestig). I was *not* able to repro on content_shell under the same conditions. I was also able to repro this on the version that thestig cited (commit aa3ce260e5248cc75e61ca7540652c74dee4bf55) on a full chrome build.
,
Jun 5 2017
Don't have the set-up to build the Debug builds with DCHECKs enabled, hence removing the Needs-TestConfirmation label. Adding "TE-NeedsTriageHelp" for further triage.
,
Jun 9 2017
,
Dec 6 2017
,
Dec 13 2017
,
Dec 13
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 13
,
Dec 13
Doesn't repro for me anymore. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by dgozman@chromium.org
, May 31 2017