New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 901237 link

Starred by 1 user
Status: WontFix
Owner:
█ harukamt@google.com
Last visit > 30 days ago
Closed: Dec 1
Cc:
metzman@chromium.org
palmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in Alloc

Project Member Reported by ClusterFuzz, Nov 2 
Detailed report: https://clusterfuzz.com/testcase?key=5362237545644032

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=575973:575974

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 2

Components: 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 2 by ClusterFuzz, Nov 2

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 3 by ClusterFuzz, Nov 2

Labels: Test-Predator-Auto-Owner
Owner: harukamt@google.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/6e7487848976f30a8bd3a216e89dafaea48bd979 (Oilpan: Add Destructor to Promptly Free Stack Allocated HeapVector and HeapDeque).

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, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5362237545644032 appears to be flaky, updating reproducibility label.
Project Member

Comment 5 by ClusterFuzz, Dec 1

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5362237545644032 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