New issue
Advanced search Search tips

Issue 839561 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

CHECK failure: !record.IsNull() in modulator_impl_base.cc

Project Member Reported by ClusterFuzz, May 3 2018

Issue description

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !record.IsNull() in modulator_impl_base.cc
  blink::ModulatorImplBase::ExecuteModule
  blink::ModuleScript::RunScript
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=555673:555674

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 3 2018

Components: Blink>HTML>Script
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, May 3 2018

Labels: Test-Predator-Auto-Owner
Owner: msi...@igalia.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/1b00299668ca6c12f6531c5af8dee00f5f96f9b9 (third_party: Make it possible to build chromium with system wayland).

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.
So far I couldn't reproduce locally.
Owner: ----
Status: Available (was: Assigned)
I just reproduced locally.
Quite flaky (crashing once per 10~30 reloads).

Also crashed on r555673, so the regression range reported by clusterfuzz was wrong. Therefore unassigning the current owner.
Labels: Test-Predator-Wrong-CLs
The auto-assigned owner was wrong due to wrong regression range due to flakiness.
Project Member

Comment 6 by ClusterFuzz, May 4 2018

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5351353887752192 appears to be flaky, updating reproducibility label.
Project Member

Comment 7 by ClusterFuzz, May 17 2018

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

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

Comment 8 by ClusterFuzz, May 17 2018

ClusterFuzz testcase 5351353887752192 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