Error message differs with lazy compilation / lazy parsing of inner functions.
Marja, can you take a look please?

Umm, this is weird.

Minimal repro:

var __v_5 = {};
__v_7 = [][0];
class C {
  method([[] = function() { __v_5 += 1; return __v_7; }()]) {
  }
};
new C().method([]);


v8$ out/Debug/d8 ../foo308.js 
../foo308.js:4: TypeError: Cannot read property 'Symbol(Symbol.iterator)' of (intermediate value)
  method([[] = function() { __v_5 += 1; return __v_7; }()]) {
                                                       ^
TypeError: Cannot read property 'Symbol(Symbol.iterator)' of (intermediate value)
    at C.method (../foo308.js:4:56)
    at ../foo308.js:7:9

v8$ out/Debug/d8 ../foo308.js --no-lazy
../foo308.js:4: TypeError: Cannot read property 'Symbol(Symbol.iterator)' of (intermediate value)(intermediate value)
  method([[] = function() { __v_5 += 1; return __v_7; }()]) {
                                                       ^
TypeError: Cannot read property 'Symbol(Symbol.iterator)' of (intermediate value)(intermediate value)
    at C.method (../foo308.js:4:56)
    at ../foo308.js:7:9


gsathya@ was touching some of these error messages lately. Any idea what this is about? Is this expected?

 Issue 763692  has been merged into this issue.

 Issue 767258  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 48202:48203.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition_turbo_opt:x64,ignition_turbo_opt_eager
  sources: d09
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=47802:47803
Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48202:48203

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

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.

Is this really fixed? Seems you marja turned off a feature, but it will be turned on again, right?

ClusterFuzz testcase 4804923870150656 is verified as fixed, so closing issue as verified.

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

Yeah, I'll turn the flag on again.

ok - then please revisit this bug when you do.

This is not at all related to the flag though - my flag just makes more functions lazy.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

ClusterFuzz testcase 4803737620316160 is still reproducing on tip-of-tree build (trunk).

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.