Direct-leak in blink::InteractiveDetector::From |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5262482567069696 Fuzzer: attekett_dom_fuzzer Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: blink::InteractiveDetector::From blink::DocumentTiming::MarkDomContentLoadedEventEnd blink::Document::FinishedParsing Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=513625:513656 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5262482567069696 Additional requirements: Requires Gestures Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Feb 3 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/2494ceb8558c07fbc505f757868e9eea0f030246 (Implement Time to Interactive Detector). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Feb 28 2018
ClusterFuzz testcase 5262482567069696 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Feb 3 2018Labels: Test-Predator-Auto-Components