-
Notifications
You must be signed in to change notification settings - Fork 574
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
"free(): invalid pointer" when running on Ubuntu x86_64 and Node.js >= v20.12.0 #6589
Comments
github-actions
bot
added
Encryption:Off
Frequency:Sometimes
Repro:Sometimes
SDK-Use:Local
labels
Apr 4, 2024
➤ PM Bot commented: Jira ticket: RJS-2790 |
This might have been the cause: realm/realm-core#7434 🤞 |
This was referenced Apr 10, 2024
I've created realm/realm-core#7604 with more information on the root cause of this crash. |
kraenhansen
changed the title
Coverage tests started crashing
"free(): invalid pointer" when running on Ubuntu x86_64 and Node.js >= v20.12.0
Apr 18, 2024
Regarding the uncorrect exit code when the subprocess spawed by
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note
If you're seeing "free(): invalid pointer" when running on Ubuntu x86_64, a valid workaround is downgrading Node.js to v20.11.1
Description
See for more information realm/realm-core#7604.
The coverage tests started crashing around March 26th, by the release of Node.js v20.12.0.
Here's an example of a failing run: https://github.com/realm/realm-js/actions/runs/8552406490/job/23433443919?pr=6587
There seem to be two issues:
npm run ci:coverage
process exits cleanly, which is unexpected from a crash.I've reproduced the crash on these Realm JS commits:
Stacktrace & log output
free(): invalid pointer
The text was updated successfully, but these errors were encountered: