internal error: entered unreachable code: Expected at least one stalled top-level await about deno

[panva]

Tested again with https://github.com/denoland/deno/releases/tag/v1.44.1, issue still persists.

[bartlomieju]

Looks like this will be fixed by #24128.

[panva]

#24128 (https://github.com/denoland/deno/releases/tag/v1.44.2) did not fix this issue

[bartlomieju]

@panva we've been investigating this issue with @nathanwhit and so far we established that the problem appeared when we upgraded from V8 12.4 to V8 12.6. The investigation leads us to believe that it might be a V8 bug, we're trying to strip down the reproduction and validate the idea.

[nathanwhit]

I was able to minimize the reproduction and I'm now fairly sure this is a V8 bug. You can see the reproducer here: https://github.com/nathanwhit/v8-async-module-hang (that relies on part of V8). There's an equivalent reproducer for deno here: https://github.com/nathanwhit/deno-async-module-hang (there are a couple tiny differences with the above due to some differences in event loops).

I've reported this upstream (here), and I'll try to update here once I hear back

[lucacasonato]

The reproduction reproduces in all versions of Deno down to at least 1.15.0 - seems to be a long standing bug in V8.

[panva]

How come in the reproduction case you only encounter it the first time the code runs in a given directory? And only since a couple releases ago?

[lucacasonato]

@panva It's timing dependant - I can reproduce it every time on an M1 MacBook Air.

Anyway, it is a confirmed upstream bug - I'm working with Shu from V8 to figure out a fix.

[bartlomieju]

The fix has landed in https://chromium-review.googlesource.com/c/v8/v8/+/5631143. We'll most likely will need to wait until the next minor release as it will require to update V8.