Issue metadata
Sign in to add a comment
|
CHECK failure: entry.code_offset >= 0 in source-position-table.cc |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6408374819487744 Fuzzer: mbarbella_js_mutation Job Type: linux_asan_d8_v8_mipsel_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: entry.code_offset >= 0 in source-position-table.cc v8::internal::SourcePositionTableBuilder::AddEntry v8::internal::SourcePositionTableBuilder::AddPosition Sanitizer: address (ASAN) Regressed: V8: 46182:46183 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6408374819487744 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 27 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
,
Jun 27 2017
,
Jun 28 2017
ClusterFuzz has detected this issue as fixed in range 46234:46235. Detailed report: https://clusterfuzz.com/testcase?key=6408374819487744 Fuzzer: mbarbella_js_mutation Job Type: linux_asan_d8_v8_mipsel_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: entry.code_offset >= 0 in source-position-table.cc v8::internal::SourcePositionTableBuilder::AddEntry v8::internal::SourcePositionTableBuilder::AddPosition Sanitizer: address (ASAN) Regressed: V8: 46182:46183 Fixed: V8: 46234:46235 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6408374819487744 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jun 28 2017
ClusterFuzz testcase 6408374819487744 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jun 28 2017
,
Jul 26 2017
,
Oct 4 2017
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 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Jun 27 2017