gapit trim uses a surprisingly large amount of memory
Open
bug
GAPIS
triaged
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 329
- PR merge metrics
- No merged PRs in 30d
Description
I have a fairly large trace, (4.8GB). If I linearize it, and then try to trim, the dependency graph is built, (and takes up a roughly an additional 4gb, which is somewhat expected). However when it goes and actually applies the dependency graph to the trace, it consumes another 14GB+ (and then crashes from an OOM).
Contributor guide
Assessment
This issue has not been assessed yet.