Sam Cao

I've reproduced this issue. I think it's a regression bug in V8.   I've fired a [bug](https://groups.google.com/g/v8-dev/c/TCGnZKjYFEI/m/uDOciJsHAQAJ) to the V8 dev.

Good news. I removed this check and the crash is gone. This private patch will be included in the new release.

> cool, thanks, great project by the way... Thank you. If possible, could you reply to that [thread](https://groups.google.com/g/v8-dev/c/TCGnZKjYFEI/m/uDOciJsHAQAJ) to get V8 dev team's attention?

A new [feature request](https://issues.chromium.org/issues/345822325) was just created. Please feel free to comment on it.

Interesting, it doesn't break in my env (also Windows 10).

I had the similar idea. * Get the heap statistics after every call. * It downgrades the performance. * It doesn't completely resolve the issue. The fundamental fix is patching...

My test shows `v8::Isolate::RequestInterrupt()` works. There is still quite a lot of work to do. Please check my email reply out and let me know if you have questions.

The memory leak issue has been fixed. I look forward to your test results.

It's been in V8. [The first journey of implementing Float16Array into V8](https://blog.seokho.dev/development/2024/03/03/V8-Float16Array.html)

* [x] Wait for Node.js v22 promoted to LTS because Node.js v20 doesn't support Float16Array. * [x] Implement `Float16` in Java. References * [FP16 from Android](https://android.googlesource.com/platform/libcore/+/master/luni/src/main/java/libcore/util/FP16.java) * [Float16 from Apache...