New issue
Advanced search Search tips

Issue 776268 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 776267
Owner:
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: current_process_commandline_ in command_line.cc

Project Member Reported by ClusterFuzz, Oct 19 2017

Issue description

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  current_process_commandline_ in command_line.cc
  base::CommandLine::ForCurrentProcess
  base::SysInfo::AmountOfPhysicalMemory
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=509892:509921

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 19 2017

Components: Internals>Core
Labels: Test-Predator-AutoComponents
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Oct 19 2017

Labels: Test-Predator-AutoOwner
Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/840b7a60cc3c5f802ca271bd167e888e7494e8aa ([Re-Land] Use GPU Discardable in Image Decode Cache).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Comment 3 by piman@chromium.org, Oct 20 2017

Mergedinto: 776267
Status: Duplicate (was: Assigned)
Project Member

Comment 4 by ClusterFuzz, Oct 25 2017

ClusterFuzz has detected this issue as fixed in range 511261:511286.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  current_process_commandline_ in command_line.cc
  base::CommandLine::ForCurrentProcess
  base::SysInfo::AmountOfPhysicalMemory
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=509892:509921
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=511261:511286

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

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Labels: -Test-Predator-AutoOwner Test-Predator-Auto-Owner

Sign in to add a comment