Experiencing runaway Ram usage while camera is on

[mccormickjason]

librealsense	2.44.0 RELEASE
OS	Windows
Name	Intel RealSense D435
Serial Number	801212070143
Firmware Version	05.12.12.100
Advanced Mode	YES
Camera Locked	YES
Usb Type Descriptor	3.2
Product Line	D400
Asic Serial Number	751313020612
Firmware Update Id	751313020612

Please provide a description of the problem

[mccormickjason]

While the stereo process is streaming, but not recording, the RAM usage on PC the camera is hooked up to experiences runaway RAM usage

[MartyG-RealSense]

Hi @mccormickjason Are you using the RealSense Viewer tool or an application that you have created yourself, please?

If it is an application that you have created yourself, what functions does it perform (for example, does it generate a point cloud).

[mccormickjason]

This was through the use of the RealSense Viewer tool only. Both the RealSense T265 and the RealSense D435 were connected directly to my laptop over USB using:

Edition Windows 10 Pro
Version 20H2
Installed on ‎7/‎05/‎2021
OS build 19042.928
Experience Windows Feature Experience Pack 120.2212.551.0

on a Lenovo Thinkpad E14 Gen 2

• Confirmed that the T265 added a static amount of RAM allocation on my device when the stream was activated.
• Confirmed that the RGB camera of the D435 added a static amount of RAM allocation when the stream was activated.
• Isolated that the Stereo camera was allocating approximately 0.3GB of RAM every second at a very stable and linear rate when its stream was activated.
• RAM allocation to Intel RealSense Viewer would remain static when the stereo camera stream was not activated.
• It would immediately return to it's RAM allocation rate of 0.3GB/s when it was activated.
• Confirmed that this occurred regardless of if the T265 was also connected.

Can also confirm that it is not my device causing the issue. A week ago, I completely lost my Lenovo Yoga 720-15ikb less than 40 minutes after initialising the same D435 (I am uncertain if it was the same build of RealSense Viewer). System crashed after leaving the D435 on in the background for about 20 minutes. BIOS would only boot after 30 minutes of waiting, implying a complete RAM failure. M.2 SSD was also a complete loss after not even registering as a disk in a separate machine.

The only remaining items are a physical fault of the camera, the RealSense Viewer tool, or a combination of the two.

[mccormickjason]

It is the D435 stereo camera that was causing the RAM allocation issue. NOT the T265.

[MartyG-RealSense]

Okay, thank you. I can continue handling the case if T265 is not involved in the problem and it is not mentioned in the case from this point onwards.

As a starting point in investigating your case, could you try disabling the two GLSL options in the Viewer's Settings interface using the instructions in the link below please and see whether that makes a positive difference to RAM usage.

#8110 (comment)

[mccormickjason]

Thanks. Have not yet had the opportunity to attempt this fix. If possible, please leave this ticket open for approximately one week.

[MartyG-RealSense]

Thanks very much for the update. Yes, it is no problem to leave this case open for a further time period. Good luck!

[MartyG-RealSense]

Hi @mccormickjason Do you have an update that you can provide about this case, please? Thanks!

[MartyG-RealSense]

Case closed due to no further comments received.