-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible memory leak? #20
Comments
I will need a reproducible test/code so that I can debug. Are you able to attach a small zip file and instructions? |
Hi. Please check memoryTest.txt for code, and Stack.txt for error, from previous post. |
any update on this? |
I didn’t have time to inspect this and without any reproducible test / repo it’s hard. Usually this is a leak in your code not with this module. |
Actually @stefansaravolac supplied some test code, will try to debug in the next couple of days.. |
Hello, I'm planing to use this project on my server, so I want to know had this issue been confirmed or fixed? |
Experienced this multiple times and just reproduced and fixed excessive memory/GC in a service using this library. |
@satazor Were you able to debug it as in your comment above? Memory leak is a problem I think. |
For anyone who is interested, until this is resolved, I've just reverted back to (a slightly modified version of): function retryForever(fn) {
return fn().catch(function(err) {
return retryForever(fn);
});
} |
We are experiencing the same problem described in this issue. We actually were not sure what was causing it until we came across this issue. |
Hi,
I'm using library(v1.1.1) on node 6.9.1. to retry when saving system errors to database.
For each created error, I create an instance of promise-retry, with options like this:
minTimeout= 6000;
maxTimeout= 10000;
retries= 9999999
When the error is created in the system, it is automatically saved to database.
When I try to run test code with 23 error instances to be created,
the node process breaks due to -heap out of memory-
(on the 8th instance created)
If I turn off library, and just save errors to database without retry,
all 23 errors are saved without memory leak.
I've attached stack excerpt and code I used to simulate memory leak.
It seems to be library bug. Could you please check this?
memoryTest.txt
Stack.txt
The text was updated successfully, but these errors were encountered: