New issue
Advanced search Search tips

Issue 697965 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Crash in v8::internal::wasm::WasmFullDecoder::DefaultValue

Project Member Reported by ClusterFuzz, Mar 2 2017

Issue description

Components: Blink>JavaScript
Labels: Test-Predator-Wrong M-58
Seems like dupe of  issue 698018 .
Project Member

Comment 2 by ClusterFuzz, Mar 6 2017

ClusterFuzz has detected this issue as fixed in range 454793:454795.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4567863668244480

Fuzzer: libfuzzer_v8_wasm_asmjs_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000001a28308
Crash State:
  v8::internal::wasm::WasmFullDecoder::DefaultValue
  v8::internal::wasm::WasmFullDecoder::InitSsaEnv
  v8::internal::wasm::WasmFullDecoder::Decode
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=454232:454244
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=454793:454795

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96MgU2jUfN1sgAjqzI3j9_Sh3pRXy_T8Ay5y2BEGqaLSMKmWp0z6HYs9VyA9Ot-_15pFQfPOL7n3aY5s2CN_519eiXFTsOCSMtCIgbE6ICgGe8tWSTTtqOwnr_SIPKLxVSztsN2Kfx6j0GlzryKtuy3amxgnMx2f_0yjUwReUQ0OJ044uJuFsQP4G6GGX0Zey2kj4egQlJFcdxZrleBpNVR84bPBac25-gMP7Z7lQPKnon6rqK9dYSi4xACgB4IZZRwgcj-8Lk9U_57lNJfutzI6k9iX3LDEfFoLPSltGr5VAbN8w0VZ427EPyGJLXjHz4xFgeYaXr-NexOgz0FjuE0QT05qXo--07KY8bJOgO4sn9Heoo?testcase_id=4567863668244480


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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 3 by ClusterFuzz, Mar 6 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 4567863668244480 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment