New issue
Advanced search Search tips

Issue 784749 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: interpreter != liftoff (0 vs fNUMBER); WasmCodeFuzzerHash=NUMBER in wasm-fuzzer-

Project Member Reported by ClusterFuzz, Nov 14 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5409920555155456

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  interpreter != liftoff (0 vs fNUMBER); WasmCodeFuzzerHash=NUMBER in wasm-fuzzer-
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=515852:515856

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5409920555155456

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Nov 14 2017

Components: Blink>JavaScript
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Nov 14 2017

Labels: Test-Predator-Auto-Owner
Owner: v8-autoroll@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/ad1474a10f76712669b926fb1e53313c9921b487 (Version 6.4.244).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 3 by ClusterFuzz, Nov 14 2017

ClusterFuzz has detected this issue as fixed in range 515946:515969.

Detailed report: https://clusterfuzz.com/testcase?key=5409920555155456

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  interpreter != liftoff (0 vs fNUMBER); WasmCodeFuzzerHash=NUMBER in wasm-fuzzer-
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=515852:515856
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=515946:515969

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5409920555155456

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 4 by ClusterFuzz, Nov 14 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5409920555155456 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