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

Issue 827889 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac , Fuchsia
Pri: 1
Type: Bug



Sign in to add a comment

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

Project Member Reported by ClusterFuzz, Apr 1 2018

Issue description

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

Fuzzer: inferno_twister
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result || flags & PartitionAllocReturnNull in partition_alloc.h
  blink::StringTraits<WTF::String>::FromV8String<blink::V8StringOneByteTrait>
  blink::V8StringToWebCoreString<WTF::String>
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: brajkumar@chromium.org
Components: Blink
Labels: M-66 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no related changes under regression range, hence adding appropriate label and requesting someone from blink team to look in to this issue.

Thanks!

Comment 2 by tkent@chromium.org, Apr 4 2018

Components: -Blink Blink>MemoryAllocator>Partition Blink>Bindings
Components: Blink>Internals
Labels: OS-Chrome OS-Fuchsia OS-Linux OS-Mac
This looks like the caller did not expect a nullptr return, but PA had to return nullptr anyway (perhaps as a matter of policy, e.g. overly large allocation requests; or of circumstances, e.g. OOM). It's unlikely to be a bug in PA per se.
Status: WontFix (was: Untriaged)
It looks like an OOM error while trying to convert a very large V8 string to a WTF::String. I'm not sure there's anything else we can do here other than crash.
Project Member

Comment 5 by ClusterFuzz, Apr 11 2018

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

Comment 6 by palmer@chromium.org, Apr 12 2018

Labels: -Needs-Feedback

Sign in to add a comment