search

QuantumEntangledAndy / neolink

An RTSP bridge to Reolink IP cameras
GNU Affero General Public License v3.0
250 stars 41 forks source link

0.6.3 High Memory Consumption until system crashed #183

Closed jerryj001 closed 2 months ago

jerryj001 commented 8 months ago

Installed 0.6.3 , Memory usage is high and constantly increasing when running with Frigate. It crashed system in the end. Restarted system several times, also change configurations of both Frigate and Neolink, didn't solve the problem. In the end, reversing back to 0.6.2 solved the problem

To Reproduce Steps to reproduce the behavior:

  1. Install 0.6.3;
  2. run with Frigate

Versions NVR software: Frigate 0.12.1 Neolink software: 0.6.2 Reolink camera model and firmware: Lumus v2.0.0.705_21052800 Ubuntu 22.04.3 LTS

Sinnedterklaas commented 8 months ago

I'm running Neolink on Home Assistant using the fork of d82m. Running this on a Intel Nuc with a celeron n3050. I had much more delay and more cpu/ram usage than version using the last 0.6.3 compared to version 0.6.2

I'm also using this with a Reolink Lumus v2.0.0.705_21052800 - so something seems to be going on with this combination.

enieuwy commented 8 months ago

Same issue. Started getting outages of all services running on my Synology NAS. Resource manager shows 9gb RAM used by neolink. Killed the container, and finally my services are responsive again.

dan-r commented 8 months ago

Same here, with my Lumus and that firmware version my delay was getting to 2+ minutes vs ~5 seconds with v0.6.1.

skywurz commented 8 months ago

Came here to say the same. I have set --restart=on-failure --memory="10g" on my container to prevent full system lockup and the container eats the 10gb and crashes every 2 days.

JC38 commented 7 months ago

Same here for the RC1 image

gogreenpower commented 7 months ago

Same issue using OMV6

omv crashes

edit: i'm using "latest", how to tell if its 0.6.2 or 0.6.3?

Beer17HWAM commented 5 months ago

Same here with Neolink 0.6.3-rc.1 on Debian Bookworm. Delay is geting more and more after new start. neolink

QuantumEntangledAndy commented 2 months ago

Hopefully this is now fixed in latest. If anyone could confirm that would be nice

JC38 commented 2 months ago

Andrew, Thanks for this information. But which latest version are you speaking about ? Is it the 0.6.3 rc1 or a newer ? If there is a newer, is it possible to add it into the releases section plz ?

Beer17HWAM commented 2 months ago

Hopefully this is now fixed in latest. If anyone could confirm that would be nice

I don't see a newer (recent) version than 0.6.3-rc.1 either. The 0.6.3-rc.1 has this memory issue: https://github.com/QuantumEntangledAndy/neolink/issues/183#issuecomment-1893949317

QuantumEntangledAndy commented 2 months ago

The very tip of the branch here I'll link the test binaries https://github.com/QuantumEntangledAndy/neolink/actions/runs/8843106799 they are at the bottom of the page

JC38 commented 2 months ago

Ok, downloaded and running as a service. Let's wait and see.

JC38 commented 2 months ago

I can see these lines into the log image What are they ? CPU is higher than rc1 and memory footprint too but I guess it could be related to the debug version. I'll check if memory used increase or not after some hours.

QuantumEntangledAndy commented 2 months ago

Oh that is to do with the push notifications. It needs to store the credentials somewhere and by default that is $HOME/.config but since you have it running as a services with no homedir it is erroring out.

JC38 commented 2 months ago

Hello,

Something happened during the night that made Neolink using all the CPU image

image It happened at 2 am. This is the day and time where there is a reboot scheduled into the Reolink E1 :-(.

For the memory, this is too early to say it is better or not. On the graph below, every lowest point corresponds to the start of the service. image