New issue
Advanced search Search tips

Issue 828302 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 10
Cc:
kylec...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 3
Type: Bug



Sign in to add a comment

CHECK failure: context_result != gpu::ContextResult::kFatalFailure in layouttest_support.cc

Project Member Reported by ClusterFuzz, Apr 3 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6528309027143680

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  context_result != gpu::ContextResult::kFatalFailure in layouttest_support.cc
  content::LayoutTestDependenciesImpl::CreateDisplayOutputSurface
  content::LayoutTestDependenciesImpl::CreateDisplayOutputSurface
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=546083:546086

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Apr 3 2018

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 2 by ClusterFuzz, Apr 3 2018

Labels: Test-Predator-Auto-Owner
Owner: kylec...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/8f76378d1ae6d9d6ce6faddc3cc7c91c6ea9e3fa (Check context result in layout tests.).

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.

Comment 3 by kylec...@chromium.org, Apr 3 2018

Labels: -Pri-1 Pri-3
This crash is expected and is just  crbug.com/817758  moved to a different spot. Someone (which is probably me) should look at why CommandBufferHelper::AllocateRingBuffer() is failing eventually.
Project Member

Comment 4 by ClusterFuzz, Apr 11 2018

Labels: OS-Mac

Comment 5 by kylec...@chromium.org, Jul 25

Cc: kylec...@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
I don't have the cycles for this anytime soon.

Comment 6 by weiliangc@chromium.org, Jul 27

Status: Available (was: Untriaged)
kylechar@, is there any place to track this bug? Do we expect this to be blocking some other bug/feature?

Comment 7 by kylec...@chromium.org, Jul 27 

I don't think this is blocking anything but is worth eventually looking into. CommandBufferHelper::AllocateRingBuffer() is failing sometimes. I think it could be an OOM error but I'm not sure if that should happen with ClusterFuzz? Maybe there is some other bug with AllocateRingBuffer() that is fixable? The main issue is I could never reproduce an authentic failure in AllocateRingBuffer() when I looked at it.
Project Member

Comment 8 by ClusterFuzz, Oct 10

Status: WontFix (was: Available)
ClusterFuzz testcase 6528309027143680 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment