Same issue as before. Client locks at random times. 8.10 beta wasn't perfect; but I could display 4 feeds without it locking up. I can't display my 12 cameras at once without issues on any of the clients.

Might be time to go back to HikVision.

DX9 released 20 years ago, and 7 years before Reolink was a business.... sometimes I wonder about Reolink and the oddball support they push.

@joseph-chircop_497308027822318

Support sent me the new APK link, unfortunately it didn't solve my issue. I'm going to install the app on a different phone to make sure my actual doorbell isnt the issue.

https://drive.google.com/file/d/1uf0G_w53SJB3H7187AbidjrO1OMMutcM/view?usp=share_link

This is the "updated" version that will show up on the google play store soon.
https://drive.google.com/file/d/1uf0G_w53SJB3H7187AbidjrO1OMMutcM/view?usp=share_link

8.8.0 is still randomly freezing the live camera views. This is the 3rd update in a row that hasn't fixed the issue.

8.5.2 is the latest version that still works as intended.

This is getting old...

DX9 released 20 years ago, and 7 years before Reolink was a business.... sometimes I wonder about Reolink and the oddball support they push.

@joseph_1979



it happens so frequently, that I set a batch file to run every 3 hours....

TASKKILL /IM Reolink.exe /F
TIMEOUT /T 5
START C:\"Program Files"\Reolink\Reolink.exe

also the same issue as posted here a few weeks back. (https://community.reolink.com/topic/5671/8-10-2-memory-leak-or-something?post_id=21871&_=1686518759084)

Is it possible to set the screen location via some user setting to force the Reolink Client application to start in a specific location? For whatever reason, the reolink client does not "remember" the last position when it's closed in Windows 11.

I always put the client on my left monitor in the lower 3rd ( vertical ultra wide). Every time you close the program or restart, the client starts on the main screen right in the middle.


If the client wouldn't crash all the time, it wouldn't be a problem. But since it does..... I've created a batch script that forces the close and reopens it, just hate that it always starts in the middle of the screen and doesn't remember the size or location..

@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 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 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 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.

@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.

@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.

I'm going to a*sume 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