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

Issue 778941 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: result || flags & PartitionAllocReturnNull in partition_alloc.h

Project Member Reported by ClusterFuzz, Oct 27 2017

Issue description

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

Fuzzer: inferno_twister
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result || flags & PartitionAllocReturnNull in partition_alloc.h
  GetHandleVerifier
  GetHandleVerifier
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=500786:500791

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: msrchandra@chromium.org pnangunoori@chromium.org
Components: Blink>MemoryAllocator>Partition
Labels: Test-Predator-Wrong M-63
Owner: palmer@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “partition_alloc.h” assigning to concern owner from GIT blame.
Suspecting Commit#
https://pdfium.googlesource.com/pdfium.git/+/79e548eb98caefd3ea0f0e4806a7abca6654e7dc%5E%21/third_party/base/allocator/partition_allocator/partition_alloc.h

@palmer -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Comment 2 by palmer@chromium.org, Oct 27 2017

Status: WontFix (was: Assigned)
The commit given in #1 doesn't make any sense; GetHandleVerifier doesn't even appear in PDFium. It could be that a Chromium renderer embedding PDFium calls GetHandleVerifier, which can call `new ActiveVerifier`, which might...? call into Partition Alloc.

But this looks like allocation simply failed due to e.g. OOM.
Project Member

Comment 3 by ClusterFuzz, Nov 3 2017

Labels: Needs-Feedback
ClusterFuzz testcase 6034421391294464 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.
Project Member

Comment 4 by ClusterFuzz, Nov 4 2017

ClusterFuzz has detected this issue as fixed in range 513950:513982.

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

Fuzzer: inferno_twister
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result || flags & PartitionAllocReturnNull in partition_alloc.h
  GetHandleVerifier
  GetHandleVerifier
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=500786:500791
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=513950:513982

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

See https://github.com/google/clusterfuzz-tools for more information.

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

Sign in to add a comment