Reolink Year in Review 2023
How ColorX Technology Turn Night into Day
Reolink App v4.43 Released
@joseph_1979 I submitted this to Reolink's support center this morning. I hope they respond.
@robert-hammond_315369854550200 I have done a ton of digging and I can only recreate this issue if I am running the Reolink client on my PC.The only thing I can tie it to is the Reolink client causing something to consume all available memory. I am currently up to version 8.12.1, but the same problem continues.If I do not have Reolink running on this computer, the issue with the memory leak does not occur, I can run all kinds of other items in the background (browers, other applications, etc..) and I never see a leak, even if I leave this machine on for weeks at a time.If I leave no other applications running, and only run the Reolink client, within a few hours, (6-10 or so), the memory leak occurs. When I close the client, the memory is not returned for free use.In Task Manager, I never see more than ~800 MB allocated to the Reolink client, which is extremely odd, but Task Manager does not always show everything.Digging deeper into the issue - When the memory leak occurs:Using poolmon with the -b switch, from a command prompt C:\> poolmon -b, I can see a huge amount of paged and non paged memory that is tied to the EtwD and Etwr tags.Below is the text of the top lines of poolmon. Again, this issue with consumption of RAM only occurs when the Reolink client is running on this computer. No other applications impact the memory useage when they are running. Memory:66885548K Avail:12313068K PageFlts: 24045 InRam Krnl:-6424K P:34528624K Commit:59647328K Limit:66885548K Peak:66885548K Pool N:6317188K P:34664856K System pool information Tag Type Allocs Frees Diff Bytes Per Alloc EtwD Paged 189742250 ( 0) 129776273 (20992) 59965977 29704426832 ( -10412368) 495 Etwr Nonp 189753884 ( 0) 129787891 (20992) 59965993 4797279440 ( -1679360) 80These tags are [censored]ociated with Windows Event Tracing. From pooltag.txt (in De[censored]s\x64\triage\ )Etwr - nt!ewt - Etw Reply Queue EntryEtwD - nt!ewt - Etw DataBlockAll I can correlate this to is there is something in the Reolink application that is causing a Windows Tracing Event to randomly request a huge number of DataBlocks (EtwD) and attempt to reply (Etwr), that is eating up all the memory from the paged and non-paged pool.I do not know what it is causing this, but it only happens with the Reolink client running.Also, the machine is up-to-date Windows 10, including all drivers and software updates for various applications, it has been scanned for viruses / malware, and there are no other issues.
I recently upgraded to v8.10.4, and the the Client software appears to have a fast memory leak.I am viewing 13 cameras in the application on the screen on my PC, and in 1-2 hours of running, the application consumes ~50 GB of RAM (yes 50 GB).The machine that runs this application is fairly robust, Windows 10 Pro, Version 22H2 (I9-9900, 64GB RAM, dual GPUs, etc...).I upgraded from Client v184.108.40.206 to v8.10.4, as the older version of the client stopped working when I installed the latest firmware with my NVR (RLN16-410, hardware H3MB18, firmware v220.127.116.11_23031645).The old Client v18.104.22.168 did not appear to have any noticeable issues with memory consumption growing, but no longer displays video streams from cameras with the newer firmware on the NVR.Has anyone else seen issues with the client while running v8.x.x and memory consumption continuing to increase?
Hi there! Join the Commnunity to get all the latest news, tips and more!