Investigate memory issues on Windows #16594
Assignees
Labels
kind/tech
A technical change.
team/client
Issue for team Client.
tech/typescript
Issue for tech TypeScript.
topic: js heap out of memory
topic: memory leak
Milestone
Comments
SevInf
added
tech/typescript
SevInf
added a commit
that referenced
this issue
Dec 6, 2022
This fixes 2 memory leaks in our test setup: 1. Jest passes every file through transform and caches the results on disk and in memory. That included every generated client as well, so they were kept in memory from the time they were first loaded until process finishes, even though they are needed only for 1 test suite. Fixed by using `transformIgnorePatterns` options in jest config. 2. `debug` library keeps a list of last 100 logs that would be used for panic error messages later. If error object gets into this list, it will keep whole jest sandbox alive until process finishes. Fixed by clearing logs on `$disconnect` Fix #16594
SevInf
added a commit
that referenced
this issue
Dec 7, 2022
This fixes 2 memory leaks in our test setup: 1. Jest passes every file through transform and caches the results on disk and in memory. That included every generated client as well, so they were kept in memory from the time they were first loaded until process finishes, even though they are needed only for 1 test suite. Fixed by using `transformIgnorePatterns` options in jest config. 2. `debug` library keeps a list of last 100 logs that would be used for panic error messages later. If error object gets into this list, it will keep whole jest sandbox alive until process finishes. Fixed by clearing logs on `$disconnect` Fix #16594
SevInf
added a commit
that referenced
this issue
Dec 7, 2022
This fixes 2 memory leaks in our test setup: 1. Jest passes every file through transform and caches the results on disk and in memory. That included every generated client as well, so they were kept in memory from the time they were first loaded until process finishes, even though they are needed only for 1 test suite. Fixed by using `transformIgnorePatterns` options in jest config. 2. `debug` library keeps a list of last 100 logs that would be used for panic error messages later. If error object gets into this list, it will keep whole jest sandbox alive until process finishes. Fixed by clearing logs on `$disconnect` Fix #16594
jkomyno
pushed a commit
that referenced
this issue
Dec 21, 2022
This fixes 2 memory leaks in our test setup: 1. Jest passes every file through transform and caches the results on disk and in memory. That included every generated client as well, so they were kept in memory from the time they were first loaded until process finishes, even though they are needed only for 1 test suite. Fixed by using `transformIgnorePatterns` options in jest config. 2. `debug` library keeps a list of last 100 logs that would be used for panic error messages later. If error object gets into this list, it will keep whole jest sandbox alive until process finishes. Fixed by clearing logs on `$disconnect` Fix #16594
jkomyno
pushed a commit
that referenced
this issue
Dec 21, 2022
This fixes 2 memory leaks in our test setup: 1. Jest passes every file through transform and caches the results on disk and in memory. That included every generated client as well, so they were kept in memory from the time they were first loaded until process finishes, even though they are needed only for 1 test suite. Fixed by using `transformIgnorePatterns` options in jest config. 2. `debug` library keeps a list of last 100 logs that would be used for panic error messages later. If error object gets into this list, it will keep whole jest sandbox alive until process finishes. Fixed by clearing logs on `$disconnect` Fix #16594
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our CI pipelines fail with out of memory issues since recently. It looks like there might be a memory leak again. We need to take a look into it and fix the problem.
The text was updated successfully, but these errors were encountered: