Skip to content
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

Neolink docker container memory leak? #322

Open
ENT108 opened this issue Nov 21, 2022 · 5 comments
Open

Neolink docker container memory leak? #322

ENT108 opened this issue Nov 21, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@ENT108
Copy link

ENT108 commented Nov 21, 2022

Describe the bug
Running docker version takes lots of memory.

To Reproduce
Run the docker with 1 camera added.

Expected behavior
Less memory consumption.

Versions
Neolink software: docker:latest
Reolink camera model and firmware: Lumus, v2.0.0.687_20102800

Screenshot 2022-11-21 at 17 55 23

@ENT108 ENT108 added the bug Something isn't working label Nov 21, 2022
@Pytonballoon810
Copy link

I have the same Problem. The docker container seemingly has a memory leak.
After 2:30 Uptime:
image

After Uptime ~ 1min:

Max 2G RAM usage

@QuantumEntangledAndy
Copy link
Collaborator

@Pytonballoon810 Please see #370 and address this issue in the right repo. (I think you meant that repo their since you use mqtt-rtsp which I don't think is in this repo)

Also I've been tracking the memory leak issue in QuantumEntangledAndy#202 and I need someone to test my latest fix it see if that helps.

@Pytonballoon810
Copy link

@QuantumEntangledAndy Is the fix on the quantumentangledandy/neolink:latest docker image? If so, i am already using that.

@QuantumEntangledAndy
Copy link
Collaborator

QuantumEntangledAndy commented Apr 17, 2024

No It's on the valgrind one at quantumentangledandy/neolink:test-valgrind. Also let's not discuss this on this thread if you have an issue with my fork best talk about it there

@Pytonballoon810
Copy link

Ok. I will test the test-valgrind image and will write about my experience on your fork in Issue#202

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants