New issue
Advanced search Search tips

Issue 921017 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
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, Jan 11

Issue description

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Fuzz target binary: 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=563693:563707

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

Issue filed automatically.

See https://www.chromium.org/developers/testing/memorysanitizer#TOC-Reproducing-ClusterFuzz-Bugs for instructions to reproduce this bug locally.
 
Project Member

Comment 1 by ClusterFuzz, Jan 11

Cc: piman@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Components: Internals>GPU>Internals
Labels: -Pri-1 Pri-2
Owner: geoffl...@chromium.org
Those are kinda hard to investigate, and not that interesting TBH, unless they block progress.
In the past I've had moderate success with limiting maximum sizes for things like command buffer Buckets (I think that should be applying to passthrough) or buffer objects (because of shadow memory), see https://cs.chromium.org/chromium/src/gpu/command_buffer/tests/fuzzer_main.cc?q=fuzzer_main.cc&sq=package:chromium&dr&l=397
Not sure if something similar is applicable here.
This is likely due to the scratch memory allocated to zero-initialize buffers.  
Status: Assigned (was: Untriaged)

Sign in to add a comment