CHECK failure: !interface_object.IsEmpty() in V8PerContextData.cpp |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6750763903877120 Fuzzer: lcamtuf_cross_fuzz Job Type: windows_asan_chrome Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: !interface_object.IsEmpty() in V8PerContextData.cpp blink::V8PerContextData::CreateWrapperFromCacheSlowCase blink::V8PerContextData::CreateWrapperFromCache Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=502379:502432 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6750763903877120 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 21 2017
,
Sep 23 2017
Testcase 6750763903877120 is a top crash on ClusterFuzz for windows platform. Please prioritize fixing this crash. Marking this crash as a Stable release blocker. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Sep 24 2017
,
Sep 25 2017
Doesn't look to be V8 but Blink related. Changing the component accordingly for help in further investigation by the respective team. Assigning to yukishiino@ based on Issue 766143 for earlier assignment and more inputs n this.
,
Sep 27 2017
,
Sep 28 2017
ClusterFuzz has detected this issue as fixed in range 504594:504637. Detailed report: https://clusterfuzz.com/testcase?key=6750763903877120 Fuzzer: lcamtuf_cross_fuzz Job Type: windows_asan_chrome Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: !interface_object.IsEmpty() in V8PerContextData.cpp blink::V8PerContextData::CreateWrapperFromCacheSlowCase blink::V8PerContextData::CreateWrapperFromCache Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=502379:502432 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=504594:504637 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6750763903877120 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.
,
Sep 29 2017
ClusterFuzz testcase 6750763903877120 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 |
|||||||
Comment 1 by pnangunoori@chromium.org
, Sep 21 2017Labels: M-63 Test-Predator-Wrong