New issue
Advanced search Search tips

Issue 915437 link

Starred by 1 user
Status: WontFix
Owner:
palmer@chromium.org
Closed: Dec 17
Cc:
palmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Clusterfuzz: Can't send XHR with 3GB POST request body

Project Member Reported by ClusterFuzz, Dec 15 
Detailed report: https://clusterfuzz.com/testcase?key=6311272557314048

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  count <= MaxElementCountInBackingStore<T>() in partition_allocator.h
  blink::XMLHttpRequest::send
  blink::V8XMLHttpRequest::SendMethodCallback
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=488740:489609

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 15

Components: Blink>JavaScript Blink>Network>XHR
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.

Comment 2 by hirosh...@chromium.org, Dec 15

Components: -Blink>JavaScript Blink>MemoryAllocator>Partition
Summary: Clusterfuzz: Can't send XHR with 3GB POST request body (was: CHECK failure: count <= MaxElementCountInBackingStore<T>() in partition_allocator.h)
The JavaScript tries to send an XHR with ~3GB (or 1~2GB?) POST data and crashes due to limitation of max memory allocation size (~2GB).
This is not OOM but hitting limit of memory allocation size, but probably WontFix?

Comment 3 by hirosh...@chromium.org, Dec 15

Labels: -Pri-1 Pri-3

Comment 4 by palmer@chromium.org, Dec 17

Owner: palmer@chromium.org
Status: WontFix (was: Untriaged)
Right, this is intentional policy.
Project Member

Comment 5 by ClusterFuzz, Dec 24

Labels: Needs-Feedback
ClusterFuzz testcase 6311272557314048 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 hirosh...@chromium.org, Dec 25

Labels: ClusterFuzz-Ignore
►

Sign in to add a comment