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

Issue 722110 link

Starred by 1 user
Status: WontFix
Owner:
palmer@chromium.org
Closed: May 2017
Cc:
█ msrchandra@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in PartitionAllocGenericFlags

Project Member Reported by ClusterFuzz, May 14 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5143888886235136

Fuzzer: afl_content_security_policy_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  PartitionAllocGenericFlags
  PartitionAllocGeneric
  BufferMalloc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=430381:430451

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


Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, May 15 2017

Cc: msrchandra@chromium.org
Labels: M-60 Test-Predator-Wrong
Owner: palmer@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "Partitions.h" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/0d001e69ad6e768eda29b9c3b7551ffaadcf6de6

@palmer -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by palmer@chromium.org, May 24 2017

Status: WontFix (was: Assigned)
I can't reproduce the bug, and a documentation change is unlikely to have resulted in such a bug. The actual functions on the stack trace have not significantly changed in years.
Project Member

Comment 3 by ClusterFuzz, Jul 14 2017

Labels: Needs-Feedback
ClusterFuzz testcase 5143888886235136 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