Issue metadata
Sign in to add a comment
|
DCHECK failure in isolate->context() == nullptr || isolate->context()->IsContext() in runtime-obje |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4650862403387392 Fuzzer: inferno_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: isolate->context() == nullptr || isolate->context()->IsContext() in runtime-obje v8::internal::Runtime_GetProperty v8::internal::Invoke Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48348:48349 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4650862403387392 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 7 2017
,
Oct 7 2017
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 7 2017
,
Oct 11 2017
ClusterFuzz has detected this issue as fixed in range 48414:48415. Detailed report: https://clusterfuzz.com/testcase?key=4650862403387392 Fuzzer: inferno_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: isolate->context() == nullptr || isolate->context()->IsContext() in runtime-obje v8::internal::Runtime_GetProperty v8::internal::Invoke Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48348:48349 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48414:48415 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4650862403387392 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.
,
Oct 11 2017
ClusterFuzz testcase 4650862403387392 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Oct 11 2017
,
Nov 3 2017
,
Nov 7 2017
,
Jan 17 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 27 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ClusterFuzz
, Oct 7 2017Owner: u...@chromium.org
Status: Assigned (was: Untriaged)