Skip to content
This repository has been archived by the owner on Sep 14, 2023. It is now read-only.

Local development with capi serve impossible - memory leak? #1054

Closed
statictype opened this issue Jun 9, 2023 · 6 comments
Closed

Local development with capi serve impossible - memory leak? #1054

statictype opened this issue Jun 9, 2023 · 6 comments
Assignees
Labels
bug Something is broken

Comments

@statictype
Copy link

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 a 2,2 GHz 6-Core Intel Core i7 MacBook Pro with node v20.0.0

Screen.Recording.2023-06-09.at.16.36.56.mov
@statictype statictype added the bug Something is broken label Jun 9, 2023
@peetzweg
Copy link
Member

Can confirm insane memory allocation on m1 pro as well.

memorysmolfast.mov

@peetzweg peetzweg changed the title Local development with capi serve impossible on Intel Mac Local development with capi serve impossible - memory leak? Jun 12, 2023
@tjjfvi tjjfvi self-assigned this Jun 12, 2023
@tjjfvi
Copy link
Contributor

tjjfvi commented Jun 12, 2023

Edit: never mind, got it working (at failing)

@tjjfvi
Copy link
Contributor

tjjfvi commented Jun 12, 2023

It's an issue with ts-node in node 20: nodejs/node#47615

@kratico
Copy link
Contributor

kratico commented Jun 12, 2023

For me, it works locally with [email protected]

@tjjfvi
Copy link
Contributor

tjjfvi commented Jun 12, 2023

Same here. @statictype @peetzweg Can you try updating and see if it also fixes it for you?

@peetzweg
Copy link
Member

Can confirm it's fixed for me once using latest node at the time 20.3.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something is broken
Projects
Status: Done
Development

No branches or pull requests

5 participants