New issue
Advanced search Search tips

Issue 914255 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 14
Cc:
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, Dec 12

Issue description

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

Fuzzer: libFuzzer_hit_test_query_fuzzer
Fuzz target binary: hit_test_query_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
  features::IsVizHitTestingSurfaceLayerEnabled
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=615635:615643

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Dec 12

Cc: sadrul@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.
Project Member

Comment 2 by ClusterFuzz, Dec 12

Components: Internals>Compositing Internals>Core
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.
Project Member

Comment 3 by ClusterFuzz, Dec 12

Labels: Test-Predator-Auto-Owner
Owner: sunxd@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/cc346947ff37b367a388f7d5252d1f77d24d1e1b (Do not offset location by region's origin in V2 hit testing).

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.
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 13

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f4de53a164a2cdaa596f56663b6702624f71cfed

commit f4de53a164a2cdaa596f56663b6702624f71cfed
Author: Xianda Sun <sunxd@chromium.org>
Date: Thu Dec 13 19:55:13 2018

Fix viz features clusterfuzz issue

Viz features can call command line to look up switches, but this lead to
a clusterfuzz failure when command line is not initialized. This patch
fixes that issue.

Bug:  914255 
Change-Id: I5d20d8dca7e331abc8db880cac0982cfc4d4432c
Reviewed-on: https://chromium-review.googlesource.com/c/1374112
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Ria Jiang <riajiang@chromium.org>
Commit-Queue: Xianda Sun <sunxd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#616403}
[modify] https://crrev.com/f4de53a164a2cdaa596f56663b6702624f71cfed/components/viz/host/hit_test/hit_test_query_fuzzer.cc

Project Member

Comment 5 by ClusterFuzz, Dec 14

ClusterFuzz has detected this issue as fixed in range 616402:616404.

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

Fuzzer: libFuzzer_hit_test_query_fuzzer
Fuzz target binary: hit_test_query_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
  features::IsVizHitTestingSurfaceLayerEnabled
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=615635:615643
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=616402:616404

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

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 6 by ClusterFuzz, Dec 14

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5258934677667840 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment