Issue metadata
Sign in to add a comment
|
CHECK failure: NumberToUint32 of kRepWord32 (Range(1, NUMBER)) cannot be changed to kRepTaggedS |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4704829162389504 Fuzzer: mbarbella_js_mutation Job Type: linux_ubsan_vptr_d8 Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: NumberToUint32 of kRepWord32 (Range(1, NUMBER)) cannot be changed to kRepTaggedS v8::internal::compiler::RepresentationChanger::TypeError v8::internal::compiler::RepresentationChanger::GetRepresentationFor Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=49849:49850 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4704829162389504 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 5 2017
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/cc07ac73a460de3d933ebe7aebf0f55b741eb5cf ([turbofan] Make sure TruncatingUseInfoFromRepresentation respects Smi representation.). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Dec 5 2017
,
Dec 6 2017
ClusterFuzz has detected this issue as fixed in range 49852:49853. Detailed report: https://clusterfuzz.com/testcase?key=4704829162389504 Fuzzer: mbarbella_js_mutation Job Type: linux_ubsan_vptr_d8 Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: NumberToUint32 of kRepWord32 (Range(1, NUMBER)) cannot be changed to kRepTaggedS v8::internal::compiler::RepresentationChanger::TypeError v8::internal::compiler::RepresentationChanger::GetRepresentationFor Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=49849:49850 Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=49852:49853 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4704829162389504 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.
,
Dec 6 2017
ClusterFuzz testcase 4704829162389504 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Dec 6 2017
,
Mar 14 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 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Dec 5 2017Labels: Test-Predator-Auto-Components