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

Issue 725764 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
not on Chrome anymore
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference WRITE in gpu::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang

Project Member Reported by ClusterFuzz, May 24 2017

Issue description

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

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  gpu::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang
  gpu::GpuWatchdogThread::OnCheckTimeout
  base::debug::TaskAnnotator::RunTask
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=456589:456626

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Cc: msrchandra@chromium.org
Components: Internals>GPU>Internals
Labels: M-60 Test-Predator-Correct-CLs
Owner: stanisc@chromium.org
Status: Assigned (was: Untriaged)
Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: stanisc
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/39b9e9062d6ddf6073c87fa799dfce737a257b27
Time: Tue Mar 14 03:15:50 2017
File gpu_watchdog_thread.cc is changed in this cl (and is part of stack frame #0, "gpu::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang"; frame #1, "gpu::GpuWatchdogThread::OnCheckTimeout")
Minimum distance from crash line to modified line: 2. (file: gpu_watchdog_thread.cc, crashed on: 286, modified: 284).

@stanisc -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.
Status: WontFix (was: Assigned)
Crashing at address 0x000000000000 is exactly what this code is intended to do - the function name is DeliberatelyTerminateToRecoverFromHang.
And it was that way before my change (which was just a small refactoring).

The real problem is running into the timeout when running the test job. That might be related to  Issue 609252 .
Project Member

Comment 3 by ClusterFuzz, Jul 14 2017

Labels: Needs-Feedback
ClusterFuzz testcase 5252960039993344 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
Labels: ClusterFuzz-Ignore
Cc: stanisc@chromium.org
 Issue 744641  has been merged into this issue.
Project Member

Comment 6 by ClusterFuzz, Oct 1 2017

Components: Internals>Core
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 7 by ClusterFuzz, Oct 26 2017

Labels: -M-60 M-64 ReleaseBlock-Beta ClusterFuzz-Top-Crash
Testcase 5705992678670336 is a top crash on ClusterFuzz for linux platform. Please prioritize fixing this crash.

Marking this crash as a Beta release blocker.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components

Sign in to add a comment