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
- OS: n/a
- Node: not claimed fixed as of 20.0
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