-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Fix UTF16ToString in TEXTDECODER=2 and MAXIMUM_MEMORY>=2GB #24335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix UTF16ToString in TEXTDECODER=2 and MAXIMUM_MEMORY>=2GB #24335
Conversation
What's up with Windows CI? Seems to be failing in download stage on several PRs. |
Looks like infra flake with the chocolaty package manager. I think its fairly rare. About as common as npm infra flake I would say. |
01cfa62
to
8a66970
Compare
8a66970
to
60b4ebb
Compare
FAIL [0.002s]: test_async_hello_v8 (test_core.instance) looks like a broken test on main branch. |
Yup, test_async_hello_v8 is unrelated. Sorry about that. |
60b4ebb
to
b7d209b
Compare
I accidentally noticed that Embind UTF-16 support was producing incorrect results with MAXIMUM_MEMORY over 2GB. Turns out, the `TextDecoder` implementation of `UTF16ToString` itself was broken in this mode due to bitwise ops, so I've added new tests and fixed this bug, slightly simplifying code in the process.
b7d209b
to
527651e
Compare
I accidentally noticed that Embind UTF-16 support was producing incorrect results with MAXIMUM_MEMORY over 2GB.
Turns out, the
TextDecoder
implementation ofUTF16ToString
itself was broken in this mode due to bitwise ops, so I've added new tests and fixed this bug, slightly simplifying code in the process.