New issue
Advanced search Search tips

Issue 739148 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Out-of-memory in gpu_angle_passthrough_fuzzer

Project Member Reported by ClusterFuzz, Jul 4 2017

Issue description

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  gpu_angle_passthrough_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=479223:479293

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


Issue filed automatically.

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

Comment 1 by piman@chromium.org, Jul 29 2017

Cc: piman@chromium.org
Labels: -Pri-1 Pri-2
Owner: geoffl...@chromium.org
Not sure if this is something real that we have to worry about or not. Without a stack trace it's hard to tell. A large enough workload could do something like this, but we should double-check that we're not doing something egregious.
Stack-overflow, Out of memory and Timeout issues are 'P2'.
Labels: Test-Predator-Wrong
Status: Assigned (was: Untriaged)
@geofflang -- Could you please look into the issue and provide an update as per Comment#2.
Thank You.
Can't repro on ToT but I could with an old revision.  OOM generated by a large glBufferData allocation and angle returns an OOM error.  Looking into returning the OOM before the allocation.

Comment 5 by mmoroz@chromium.org, Oct 24 2017

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

(bulk edit)
Project Member

Comment 6 by ClusterFuzz, Oct 25 2017

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