-
Notifications
You must be signed in to change notification settings - Fork 510
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
[Node.JS] Memory leak - Server reaches 100% memory after 5 or 6 days #741
Comments
Additional info: Each time an image is scanned, the memory increases by approximately 150 MB and it never decreases, same with express it's the same |
Are you loading the model over and over with no disposal?
El El mar, may. 2, 2023 a la(s) 1:27 p.m., Madrix ***@***.***>
escribió:
… Additional info: Each time an image is scanned, the memory increases by
approximately 150 MB and it never decreases, same with express it's the same
—
Reply to this email directly, view it on GitHub
<#741 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHTOJO5FW7GYFEGIMNRKX3XEFG2XANCNFSM6AAAAAAXPOKVIU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@GantMan you mean that
Will it work? |
It seems to work with this code: I modified it a little because the one put in demo it did not work for me:
After a few days, it takes 800MB of memory, at the start it is 150MB of memory, it seems that there is still a memory leak but it goes up very slowly, at least it does not go up to 30GB in 4 days |
I had the same problem with memory, everytime when I upload image, program will consume more and more memory. |
Hello i am having this too any solution ? |
Hi
With the http server below, my server with 32 GB of memory almost reaches 100% of memory used after 4 to 6 days, do you know where the problem could come from?
In the browser just type this: http://x.x.x.x:3000/?url=https://test.domain.com/images.jpg
It's a pity that there is a memory leak because the detection works well
The text was updated successfully, but these errors were encountered: