pubsuffix.js using a lot of memory
See original GitHub issueHi Guys,
I had a memory leak in my application and debugging it i found a few problems.
beside the leak in question i found that pubsuffix.js
is taking a lot of memory allocation.
I don`t know if i have read the logs correctly but it is a big allocation in arrays and strings.
Tracking problems i found the following issues that i think are related: https://github.com/request/request/issues/792 https://github.com/SalesforceEng/tough-cookie/issues/12
Is there anyway we can improve the code? if you guys want, i can send a heapshoot from my application
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:31 (7 by maintainers)
Top Results From Across the Web
Why does Node.js have incremental memory usage?
Seeing an increased memory footprint by a Node.js application is completely normal behaviour. Node.js constantly analyses your running code, ...
Read more >Troubleshooting large memory usage (Node.js)
If you installed the New Relic Node.js agent and your application's memory usage increases read this troubleshooting doc for potential causes and solutions....
Read more >How to Find, Fix, and Prevent Node.js Memory Leaks
Memory management for any application is essential. This post looks at what memory leaks are and how to avoid them in Node.js applications....
Read more >Avoiding Memory Leaks in Node.js: Best Practices for ...
Discover what memory leaks are and how to avoid them in your Node.js application.
Read more >Memory management - JavaScript - MDN Web Docs
In contrast, JavaScript automatically allocates memory when ... are not — and over time, the Map may accumulate a lot of useless entries....
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
@ianpogi5 The module i was using was
request
but now i’m usinggot
in replacement. https://www.npmjs.com/package/gotgot
doesn’t use this module, so this problem does not exist there.@luanmuniz were you able to deploy in production? how? as of today’s release, Meteor 1.3 only supports node v0.10.41. Deploying to a node 4.x.x or higher will result to a fibers@1.0.5 dependency error.