You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project ran across the bug described in https://bugs.chromium.org/p/v8/issues/detail?id=13891. As of this writing, It seems to be fixed, in some form, but it's not yet closed in the Chromium issue tracker, nor (obviously) is there a Node release with the fix.
Once there is in fact a Node release, we should verify the fix by undoing the workaround in EventSink.js, and doing heap dumps with a debugger attached.
Environment
OS: n/a
Node: not claimed fixed as of 20.0
The text was updated successfully, but these errors were encountered:
The bug I filed was duped into https://issues.chromium.org/issues/42203677. That bug is listed as still open, but based on the linked test case which runs in your local browser, it looks like the bug is actually fixed. Unclear when, and so also unclear if Node would have picked up the fix yet.
I just did a test with Node v22, and it looks like the problem is fixed there. Unfortunately, we can't rely on v22 being available everywhere we want to run, yet, so I'm leaving this issue open for now.
Describe the bug
This project ran across the bug described in https://bugs.chromium.org/p/v8/issues/detail?id=13891. As of this writing, It seems to be fixed, in some form, but it's not yet closed in the Chromium issue tracker, nor (obviously) is there a Node release with the fix.
Once there is in fact a Node release, we should verify the fix by undoing the workaround in
EventSink.js
, and doing heap dumps with a debugger attached.Environment
The text was updated successfully, but these errors were encountered: