This repository has been archived by the owner on Sep 14, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
Local development with capi serve
impossible - memory leak?
#1054
Labels
bug
Something is broken
Comments
Can confirm insane memory allocation on m1 pro as well. memorysmolfast.mov |
peetzweg
changed the title
Local development with
Local development with Jun 12, 2023
capi serve
impossible on Intel Maccapi serve
impossible - memory leak?
Edit: never mind, got it working (at failing) |
It's an issue with ts-node in node 20: nodejs/node#47615 |
For me, it works locally with |
Same here. @statictype @peetzweg Can you try updating and see if it also fixes it for you? |
Can confirm it's fixed for me once using latest node at the time |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When trying to work with a local binary via capi on an Intel Mac, memory usage grows indefinitely.
Tried with the
capi:dev
command as defined here here on a2,2 GHz 6-Core Intel Core i7
MacBook Pro with nodev20.0.0
Screen.Recording.2023-06-09.at.16.36.56.mov
The text was updated successfully, but these errors were encountered: