New issue
Advanced search Search tips

Issue 846565 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: !GetPersistentRegion()->NumberOfPersistents() in thread_state.cc

Project Member Reported by ClusterFuzz, May 25 2018

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !GetPersistentRegion()->NumberOfPersistents() in thread_state.cc
  blink::ThreadState::RunTerminationGC
  blink::ThreadState::DetachCurrentThread
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=561417:561418

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

Additional requirements: Requires HTTP

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 25 2018

Labels: OS-Android
Project Member

Comment 2 by ClusterFuzz, May 25 2018

Components: Blink>MemoryAllocator>GarbageCollection Platform
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, May 25 2018

Labels: Test-Predator-Auto-Owner
Owner: keishi@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e3aac921d7937d5be6c962532f3d28d608824b67 (Oilpan: Clear all Persistents on thread termination).

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 4 by keishi@chromium.org, May 25 2018

Status: Started (was: Assigned)
Project Member

Comment 5 by ClusterFuzz, May 27 2018

Labels: OS-Windows
Project Member

Comment 6 by ClusterFuzz, May 28 2018

ClusterFuzz has detected this issue as fixed in range 562203:562204.

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

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !GetPersistentRegion()->NumberOfPersistents() in thread_state.cc
  blink::ThreadState::RunTerminationGC
  blink::ThreadState::DetachCurrentThread
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=561417:561418
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=562203:562204

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

Additional requirements: Requires HTTP

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 7 by ClusterFuzz, May 28 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Started)
ClusterFuzz testcase 5194923541004288 is verified as fixed, so closing issue as verified.

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

Sign in to add a comment