Direct-leak in blink::Node::SetLayoutObject |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5049011686604800 Fuzzer: inferno_twister_c Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: blink::Node::SetLayoutObject blink::LayoutTreeBuilderForText::CreateLayoutObject blink::Text::AttachLayoutTree Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=209699:209703 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5049011686604800 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Feb 6 2018
Unactionable without either a repro or a regression range. Please stop filing bug like this.
,
Feb 7 2018
eae@, just wondering, this seems to be a reproducible test case from ClusterFuzz and there is 'Unminimized Testcase' attached to the report (https://clusterfuzz.com/v2/testcase-detail/5049011686604800?noredirect=1). If this test case doesn't make sense then you want us to update CF team not to file these kind of reports? mmoroz@, any inputs here? Thank you!
,
Feb 13 2018
ClusterFuzz testcase 5049011686604800 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace. |
||||
►
Sign in to add a comment |
||||
Comment 1 by brajkumar@chromium.org
, Feb 6 2018Components: Blink>Layout
Labels: -Pri-2 M-64 Test-Predator-Wrong CF-NeedsTriage Pri-1