New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 708316 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Not on Chrome anymore
Closed: Apr 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: false in browser_process_impl.cc

Project Member Reported by ClusterFuzz, Apr 4 2017

Issue description

Labels: Test-Predator-Wrong M-58
Owner: dgn@chromium.org
Status: Assigned (was: Untriaged)
As per existing issue 625646, assigning to dgn@.please take a look and duplicate if both are same root cause.
Thank you
Project Member

Comment 2 by ClusterFuzz, Apr 18 2017

ClusterFuzz has detected this issue as fixed in range 464942:464964.

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

Fuzzer: meacer_chromebot_extensions
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in browser_process_impl.cc
  BrowserProcessImpl::OnKeepAliveStateChanged
  KeepAliveRegistry::OnKeepAliveStateChanged
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=448729:448971
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=464942:464964

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94sZ9SRf64Ly4kzMx-9oyn6mKJe86fK16d6j1o7q0nSh3sT1KxBPJNmcf6bsVnMkM6esDc5D0EDf0Hnrr6lHHAVNouPumcQO-TZDYqrQF0MP41By4R_csicMVOKTBiHj6nz4Opvl3tX-ArqLx8BIovSq5b9-12lZoIny7k6VsnSIZc53yTI2fNENbfPVnnDW3XHER-wEf1ls3Si8yL8sOAn9gWaamdfqoB6gtTvANtFfnSuxgTCnk415td8NKXcC35s7Z-0P4INofeAxHRSlf7mDDcfK5VY5PEmOLfqmTq0vu14RVe5FhrhCyE2NG8B8N8E0iIdfgak9Hd4Tsovheb05R2OE-mIMDLnMTJ3fWrGKH_2fYQdxQbnBWa8WpIl8d8nr3WNeUUeLaoamMV9KZUUETIdZg?testcase_id=5848676795940864


Additional requirements: Requires Gestures

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 3 by ClusterFuzz, Apr 18 2017

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

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

Sign in to add a comment