8.10.2 Memory leak or something....

[KS]

I'm going to assume this client ( and past few versions) has some sort of memory leak or the process isn't releasing the memory back to the system.

As after 3 hours or so, my client shows a 30-45 second delay from what actually happens in real-time. Shortly after that, it becomes unresponsive and will not close the application from the X. You have to use the task manager and close the Reolink.exe that uses the most memory before the other sessions of reolink.exe close. Then you can reopen it with everything working fine for a little while.

Even when the client locks up, the task manager shows the reolink.exe climbing steadily in memory usage.

Here is the start at around 1:30 PM



Here is the end where the client locks up and becomes unresponsive. About 4:20 PM

[joseph_1979]

@ks Would you be able to grant higher priority and check again. Task Manager--->Detail--->find processes reolink.exe.......right click and set priority.....say high or above normal. I am running this beta for a number of days and have no mem issue. I can see that you have a lot of services running on your PC.

You can use the Windows 'perfmon' to monitor the mem usage and leaks by including the counters pool nonpaged/paged bytes and usage of paging file.

[KS]

@joseph_1979 I'll run it today with a higher priority. As for the amount of process, It's a new Windows 11 install with Discord, Reolink, PIA, and Adobe Creative installed ( and drivers). but that's about it.

[joseph_1979]

@ks on all the reolink processes. It opens 5 processes. Which Reolink version you are running?

[KS]

@joseph_1979 it is on all 5, just didn't want to upload 5 images showing what I did. and the version is 8.10.2 but I've been locking up on the "new" clients since 8.8.5.

[joseph_1979]

@ks There is the 8.10.3..........and in this they have added the full screen icon at the bottom right hand side. So you had this issue also on the 8.8.5?

Presumably you have installed all Win updates.

[KS]

@joseph_1979 negative, 8.8.5 is the last version that doesn't lock up for me. and yes I have all the updates, also this clean OS install is about 1 week old.

[joseph_1979]

@ks If this re-occurs then roll back to 8.8.5. I am on 8.10.3 and have an issue with the stream mode resolution, always defaulting to Fluent. I informed support to fix it but they told me that they cannot give any date when this shall be fixed.

[KS]

@joseph_1979 I hear ya. It's kinda odd that they keep releasing these clients with the same issues ( locking up and black screens). I guess not enough people use the client on a daily basis to monitor a remote NVR.

[joseph_1979]

@ks There are but they refrain from upgrading.........it's working so don't bother to upgrade. Recall that upgrades bring new problems. The days when suppliers used to spend long period of testing have gone.......release and we will fix when customers complain.

[KS]

@joseph_1979 yes, but that's a mentality not a standard practice. If you can't fix something so evident 5 versions ago; why would you keep "adding" features on top of other issues... New people coming to Reolink, downloads the client they show available, which is not the one from a year ago.

[joseph_1979]

@ks I fully agree but this is the reality. To be first on the market. I go through this with a lot of well known suppliers....equipment running in millions of Euros.

[Crimp On_62210811129]

Is this on Windows 10 or Windows 11?
Have you ever observed memory usage over time with no cameras showing Live View?
(I am doing that on Windows 10 right now, and will report in several hours.)

[KS]

@crimp-on_62210811129 Windows 11 Pro, and I have not tried the client without showing the live view. It's literally the only reason I use the desktop client; is to view the cameras. and I can't event display all the cameras (12 in total) because the client locks up faster when showing more.

[Skeptouchous]

Definitely some kind of memory leak. Windows 11 Pro, 16gb RAM and Reolink hogs more and more RAM over time, leading Microsoft Edge to crash because there’s not enough RAM as a result of Reolink Client’s leak. This needs to be fixed.

[joseph_1979]

@skeptouchous Submit your issue to support on support @ reolink . com. Include as much information as possible.