Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Likely memory leak
See original GitHub issueJust did a release that swapped compression for "shrink-ray-current": "4.1.2", and this is the resulting memory (auto restart on a max memory limit drops it down)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10
Top Results From Across the Web
How do I check for memory leaks, and what should I do to stop ...
To find a memory leak, you've got to look at the system's RAM usage. This can be accomplished in Windows by using the...
Read more >Memory leak - Wikipedia
In computer science, a memory leak is a type of resource leak that occurs when a computer program incorrectly manages memory allocations in...
Read more >Java Memory Leaks: Solutions, Tools, Tutorials & More - Stackify
We put together this guide to help you understand how, why, and where Java memory leaks happen – and what you can do...
Read more >How To Detect and Prevent Memory Leaks | Scout APM Blog
Memory leak is the gradual loss of available computer memory when a program repeatedly fails to return memory it obtained for temporary use....
Read more >Is this very likely to create a memory leak in Tomcat?
As for the memory leak, it is produced by Axis, not You. But your context startup fails with out of heap memory, which...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
+1, any info about this or whether it’s going to be fixed?
Brotli support seems to be one of the main benefits of shrink-ray-current compared to the compression library. If anyone else is looking for dynamic brotli compression of Express responses but are worried about issues in shrink-ray-current issue tracker, compression-next seems to be an npm publish of the most promising PR for adding brotli support in the main compression library. In any case, it seems the only realistic options right now for dynamic brotli compression of Express responses are shrink-ray-current and compression-next.