New issue
Advanced search Search tips

Issue 892074 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 867522
Owner:
Closed: Oct 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: state_ == kDetached || !is_promise_called_ || !GetScriptState()->ContextIsValid(

Project Member Reported by ClusterFuzz, Oct 4

Issue description

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  state_ == kDetached || !is_promise_called_ || !GetScriptState()->ContextIsValid(
  blink::ScriptPromiseResolver::~ScriptPromiseResolver
  blink::GarbageCollectedFinalized<blink::ScriptPromiseResolver>::FinalizeGarbageC
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=566155:566164

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 4

Components: Blink>Bindings
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.
Cc: kkaluri@chromium.org
Labels: M-70 Test-Predator-Wrong
Owner: peria@chromium.org
Status: Assigned (was: Untriaged)
Predator & CL could not provide any possible suspects.

Using Code search for the file, "script_promise_resolver.h" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/8d9ab2bffbc57614331bc24edb50ff4b747238bd

peria@ -- 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!
Mergedinto: 867522
Status: Duplicate (was: Assigned)
This issue is duplicate with the  issue 867522 
and hence the test looks flaky, due to lifetime management.
I expect it'll be fixed when the unified GC is enabled by default.
 Issue 893027  has been merged into this issue.

Sign in to add a comment