New issue
Advanced search Search tips

Issue 911037 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in Alloc

Project Member Reported by ClusterFuzz, Dec 3

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6652271187984384

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)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=543123:543138

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6652271187984384

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Dec 3

Cc: metzman@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 2 by ClusterFuzz, Dec 3

Components: Blink>CSS Blink>MemoryAllocator>Partition
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 3 by ClusterFuzz, Dec 3

Labels: Test-Predator-Auto-Owner
Owner: ikilpatrick@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/edcaa42b78d784492c60379322c8697102fe13a8 (Remove -webkit-box-flex-group property.).

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.
Project Member

Comment 4 by ClusterFuzz, Jan 12

ClusterFuzz has detected this issue as fixed in range 622094:622103.

Detailed report: https://clusterfuzz.com/testcase?key=6652271187984384

Fuzzer: libFuzzer_css_parser_proto_fuzzer
Fuzz target binary: 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)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=543123:543138
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=622094:622103

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6652271187984384

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 5 by ClusterFuzz, Jan 12

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6652271187984384 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