New issue
Advanced search Search tips

Issue 873859 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in content::RenderThreadImpl::RequestNewLayerTreeFrameSink

Project Member Reported by ClusterFuzz, Aug 13

Issue description

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

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000001
Crash State:
  content::RenderThreadImpl::RequestNewLayerTreeFrameSink
  content::RenderWidget::RequestNewLayerTreeFrameSink
  content::LayerTreeView::RequestNewLayerTreeFrameSink
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=582653:582655

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Aug 13

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, Aug 13

Cc: sugoi@google.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Remove OSMesa from the chromium repo by sugoi@google.com - https://chromium.googlesource.com/chromium/src/+/0f21886190d0c27515faec2ada23541b936fb0f3

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
Cc: kylec...@chromium.org kkaluri@chromium.org
Labels: M-70
Owner: danakj@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "render_thread_impl.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/7b631be2a32b3981b8c9160a5335372e4149e706

danakj@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!
Cc: -sugoi@google.com danakj@google.com
Owner: sugoi@chromium.org
danakj is OOO. Anyways, the test has --use-gl=osmesa which got removed in https://crrev.com/c/1128207 by sugoi@.
Where does this "--use-gl=osmesa" come from? Clusterfuzz was supposed to have switched its tests to SwiftShader a while ago, no?
I'm not sure how ClusterFuzz puts together the command line. I still see --use-gl=osmesa in code search, I'm not sure if that's the problem here but it's definitely a problem.

https://cs.chromium.org/search/?q=%22use-gl%3Dosmesa%22&sq=package:chromium&type=cs
Thanks Kyle. Yes, I had seen this, but I don't think we use stuff from Native Client in this test. I *think* NaCl is already deprecated, but I don't know for sure.
Status: WontFix (was: Assigned)
Testcase will persist having --use-gl=osmesa, so marking WontFix to close
Project Member

Comment 9 by ClusterFuzz, Sep 13

Labels: Needs-Feedback
ClusterFuzz testcase 6260064432947200 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.

Sign in to add a comment