Direct-leak in Alloc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5567956522893312 Fuzzer: libFuzzer_css_parser_proto_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: Alloc blink::MediaQuerySet::Create blink::MediaQueryParser::MediaQueryParser Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5567956522893312 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 17
Predator and CL could not provide any possible suspects. Using Code Search for the file, "partition_alloc.h" suspecting the below Cl might have caused this issue Suspect CL: https://chromium.googlesource.com/chromium/src/+/7bd9d693667d585c44d2d29666860c678c19bc83 palmer@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Thanks!
,
Oct 17
I don't think my change would cause this. See if perhaps whoever owns blink::MediaQuerySet::Create knows what it is.
,
Oct 29
ClusterFuzz has detected this issue as fixed in range 603409:603410. Detailed report: https://clusterfuzz.com/testcase?key=5567956522893312 Fuzzer: libFuzzer_css_parser_proto_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: Alloc blink::MediaQuerySet::Create blink::MediaQueryParser::MediaQueryParser Sanitizer: address (ASAN) Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=603409:603410 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5567956522893312 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Oct 29
ClusterFuzz testcase 5567956522893312 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Oct 16Labels: ClusterFuzz-Auto-CC