search

thirtythreeforty / neolink

An RTSP bridge to Reolink IP cameras
https://www.thirtythreeforty.net/posts/2020/05/hacking-reolink-cameras-for-fun-and-profit/
GNU Affero General Public License v3.0
890 stars 147 forks source link

Neolink docker container memory leak? #322

Open ENT108 opened 1 year ago

ENT108 commented 1 year ago

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

Pytonballoon810 commented 5 months ago

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 commented 5 months ago

@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 https://github.com/QuantumEntangledAndy/neolink/issues/202 and I need someone to test my latest fix it see if that helps.

Pytonballoon810 commented 5 months ago

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

QuantumEntangledAndy commented 5 months ago

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 commented 5 months ago

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