Stack-overflow in logging::ShouldCreateLogMessage |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4753844257685504 Fuzzer: inferno_layout_test_unmodified Job Type: mac_asan_chrome Platform Id: mac Crash Type: Stack-overflow Crash Address: 0x7fff5b5fbff8 Crash State: logging::ShouldCreateLogMessage blink::Element::CanGeneratePseudoElement blink::StyleResolver::CreatePseudoElementIfNeeded Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4753844257685504 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jun 15 2018
,
Jun 15 2018
It's not unlikely this change modified the callstack in this case: https://crrev.com/70e693f2345a123d2d05071b73aa20783abc8a73 However, this is a stack overflow in a deep tree with recursive algorithms.
,
Jun 19 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label. |
||||
►
Sign in to add a comment |
||||
Comment 1 by brajkumar@chromium.org
, Jun 15 2018Components: Blink>CSS
Labels: M-69 Test-Predator-Wrong CF-NeedsTriage