Issue metadata
Sign in to add a comment
|
DCHECK failure in IsWasmExportedFunction(object) in wasm-objects.cc |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4973175388766208 Fuzzer: libFuzzer_v8_wasm_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: IsWasmExportedFunction(object) in wasm-objects.cc v8::internal::WasmExportedFunction::cast cast<v8::internal::Object> Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=500422:500485 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4973175388766208 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 9 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
,
Sep 9 2017
,
Sep 10 2017
,
Sep 12 2017
ClusterFuzz has detected this issue as fixed in range 500938:500987. Detailed report: https://clusterfuzz.com/testcase?key=4973175388766208 Fuzzer: libFuzzer_v8_wasm_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: IsWasmExportedFunction(object) in wasm-objects.cc v8::internal::WasmExportedFunction::cast cast<v8::internal::Object> Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=500422:500485 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=500938:500987 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4973175388766208 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.
,
Sep 12 2017
ClusterFuzz testcase 4973175388766208 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Sep 12 2017
,
Sep 15 2017
,
Sep 15 2017
This bug requires manual review: M62 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 15 2017
Approving merge for M62. Branch:3202
,
Sep 19 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 20 2017
Unclear what needs to be merged here. Removing approved and adding Merge-TBD
,
Sep 21 2017
Looks like a trunk regression based on regression range: https://chromium.googlesource.com/chromium/src/+log/aaeccdba2b242b391fd763b1fa31aca44582abed..b308ebb13a4ef412e972d45d89be402ca05cd63a?pretty=fuller&n=10000 I don't think a merge is required here.
,
Sep 25 2017
Thanks - removing Merge-TBD label.
,
Oct 5 2017
,
Dec 19 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
,
Mar 27 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Sep 9 2017