Abrt in content::GpuDataManagerImplPrivate::FallBackToNextGpuMode |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5013109233942528 Fuzzer: ipc_fuzzer_mut Job Type: linux_asan_chrome_ipc Platform Id: linux Crash Type: Abrt Crash Address: 0x053900042037 Crash State: content::GpuDataManagerImplPrivate::FallBackToNextGpuMode content::GpuDataManagerImpl::FallBackToNextGpuMode content::GpuProcessHost::RecordProcessCrash Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_ipc&range=607688:607705 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5013109233942528 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Nov 14
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ee9dfa9f040d05d82a29464202b4c226351a892f (Correctly handle GPU process launch failure). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Nov 15
@inferno: it looks like this fuzzer doesn't properly set the command line, or something, causing the GPU process to fail to launch. Prior to my patch this would spin infinitely hiding the issue. Where/how can I find the owner of this fuzzer so that I can help fix this?
,
Nov 19
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Nov 14Labels: Test-Predator-Auto-Components