New issue
Advanced search Search tips

Issue 844342 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Fatal error in

Project Member Reported by ClusterFuzz, May 18 2018

Issue description

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

Fuzzer: ochang_js_fuzzer_win
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Fatal error
Crash Address: 
Crash State:
  
  v8::platform::PrintStackTrace
  v8::internal::Runtime_DeserializeWasmModule
  v8::internal::DefaultEmbeddedBlobSize
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=51276:51277

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, May 18 2018

Labels: Test-Predator-Auto-Owner
Owner: cbruni@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/52b3b491a55f5f3233ca78e0c22c37384b92670e ([errors] Use FATAL macro where possible).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Comment 2 by cbruni@chromium.org, May 23 2018

Cc: cbruni@chromium.org
Owner: ahaas@chromium.org
Status: WontFix (was: Assigned)
Clusterfuzz seems to be keen on circumventing our builtins whitelisting:

let __v_39146 = `onmessage = function(msg) {
    let {serialized_m1, m1_bytes} = msg;
    let m1_clone = %DeserializeWasmModule(serialized_m1, m1_bytes);
  }`;
let __v_39147 = new Worker(__v_39146);
  __v_39147.postMessage({
  });


Project Member

Comment 3 by ClusterFuzz, May 30 2018

Labels: Needs-Feedback
ClusterFuzz testcase 5701272523767808 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
 Issue 873601  has been merged into this issue.
Project Member

Comment 5 by ClusterFuzz, Aug 17

Labels: Fuzz-Blocker ReleaseBlock-Beta M-70
This crash occurs very frequently on android and windows platforms and is likely preventing the fuzzer ochang_js_fuzzer_win 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.
Labels: ClusterFuzz-Ignore
Labels: -ReleaseBlock-Beta

Sign in to add a comment