New issue
Advanced search Search tips

Issue 830172 link

Starred by 1 user
Status: WontFix
Owner:
yiyix@chromium.org
Closed: Apr 2018
Cc:
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Sanitizer CHECK failure in "((MprotectNoAccess((uptr)guard_start_, guard_size_))) != (0)" (0x0, 0x0)

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  "((MprotectNoAccess((uptr)guard_start_, guard_size_))) != (0)" (0x0, 0x0)
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=541644:541645

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Apr 7 2018

Labels: Test-Predator-Auto-Owner
Owner: yiyix@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/f27d6caeb8f4b14a3651eebc429684d9f9bd5b34 (Update RenderFrameMetadataProvider creation time).

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.
Project Member

Comment 2 by ClusterFuzz, Apr 7 2018

Components: Internals>Core Internals>GPU>Internals
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 3 by ClusterFuzz, Apr 21 2018

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6458749984964608 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