Issue metadata
Sign in to add a comment
|
DCHECK failure in result in int64-lowering.cc |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4618316547883008 Fuzzer: binaryen_wasm_fuzzer Job Type: linux_asan_d8_v8_arm_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: result in int64-lowering.cc V8_Dcheck v8::internal::compiler::Int64Lowering::LowerNode Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm_dbg&range=51674:51675 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4618316547883008 Issue manually filed by: mstarzinger See https://github.com/google/clusterfuzz-tools for more information.
,
Jun 28 2018
,
Jun 28 2018
,
Jun 28 2018
,
Jul 18
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Jul 20
This crash occurs very frequently on linux platform and is likely preventing the fuzzer binaryen_wasm_fuzzer from making much progress. Fixing this will allow more bugs to be found. Marking this bug as a blocker for next Beta release. If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.
,
Jul 21
,
Jul 30
Testcase 5581456982933504 failed to reproduce the crash. Please inspect the program output at https://clusterfuzz.com/testcase?key=5581456982933504.
,
Jul 30
,
Jul 31
ClusterFuzz has detected this issue as fixed in range 54795:54796. Detailed report: https://clusterfuzz.com/testcase?key=4618316547883008 Fuzzer: binaryen_wasm_fuzzer Job Type: linux_asan_d8_v8_arm_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: result in int64-lowering.cc V8_Dcheck v8::internal::compiler::Int64Lowering::LowerNode Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm_dbg&range=51674:51675 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm_dbg&range=54795:54796 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4618316547883008 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.
,
Jul 31
ClusterFuzz testcase 4618316547883008 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jul 31
,
Aug 7
ClusterFuzz testcase 6347432926117888 is still reproducing on tip-of-tree build (trunk). Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.
,
Aug 8
Regession CL: https://chromium.googlesource.com/v8/v8/+log/658af9dd7a4c433b0d79d8034eb5dae0ac39307e..ad3d0ba83cc416b017a09fa22bd8c277c8862adb?pretty=fuller&n=10000 May be Fixed CL: https://chromium.googlesource.com/v8/v8/+log/9ba2a0a2817348f25510291dcf61e008fa1733b6..6f23c89e4fce9f5c08a135479f6a1cdb91cb0116?pretty=fuller&n=10000
,
Aug 16
,
Nov 6
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 mstarzinger@chromium.org
, Jun 28 2018Owner: gdeepti@chromium.org
Status: Assigned (was: Untriaged)