You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I kept getting OOM exceptions from node when trying to run glint via pnpm lint:types (package.json "lint:types": "glint"), so I kept increasing the amount of memory used -- I finally ended up with
NODE_OPTIONS="--max-old-space-size=12000" pnpm lint:types # or just pnpm glint directly
And I forgot the process was running cause prior attempts at increase the node ram were getting slower and slower -- this ultimately took 36 minutes before the OOM error occurred.
I was ultimately trying to debug performance, and eventually ran:
Thanks for the report; this seems like a case where Glint should be bailing and is not! Do you happen to have a minimal reproduction of this?
Aside: In the future, please copy and paste the output rather than sharing a screenshot. Screenshots are fundamentally not accessible to lots of folks who may need to interact with the repo. I happen to be well-sighted, but not everyone is!
This was a goofy discovery 😅
I kept getting OOM exceptions from node when trying to run
glint
viapnpm lint:types
(package.json"lint:types": "glint"
), so I kept increasing the amount of memory used -- I finally ended up withAnd I forgot the process was running cause prior attempts at increase the node ram were getting slower and slower -- this ultimately took 36 minutes before the OOM error occurred.
I was ultimately trying to debug performance, and eventually ran:
(or something to that effect)
And
tsc
provided me the error right away:So, from my perspective, it looks like
glint
is trying to do something and continuing to do something even thoughttsc
should error? idk.The text was updated successfully, but these errors were encountered: