Windows 10 debug assertion failed error

[mkelrajt]

---

Required Info
Camera Model	D435i
Firmware Version	05.12.15.50
Operating System & Version	Win 10
Platform	PC
SDK Version	2.50.0
Language	C/C++

Issue Description

While testing librealsense2 SDK release v.2.50.0 I've encountered the "Debug assertion failed error".

The error only occurs in examples and tools that use openGL library (realsense-viewer, rs-gl) and that are built with Debug configuration and in which GLSL for processing is used.
When built with Release configuration no error is reported, however a memory leak seems to occur when GLSL for processing is used.

Debug assertion error has not occured when running realsense-viever or rs-gl example from librealsense2 SDK v2.49.0. The possible memory leak is still present on v2.49.0.
A similar error does not occur for debug configurations on Ubuntu 18.04.

Ways to reproduce:
• Download librealsense2 v2.50.0 source from github
• Checkout to tag v2.50.0
• Use Cmake to configure project
• Open project in Visual Studio
• Build project
• Run realsense-viewer in debug mode
○ Go to settings: check Use GLSL for rendering
○ Start depth stream
○ No error
○ Go to settings. Check use GLSL for processing
○ Start depth stream
○ Debug assertion error occurs

I am aware that the GLSL memory leak has been reported before #8110
The debug assertion error could be related to the memory leak since both occur when GLSL is used for processing.
I've also tried the latest commit on the development branch and the assertion debug error occurs there also.

[MartyG-RealSense]

Hi @mkelrajt Yes, a memory leak when GLSL is enabled in the Viewer is a known issue for a small number of RealSense users. When it occurs, there is no fix for it other than to disable GLSL in the Viewer's settings interface.

If the two GLSL options are disabled in the Viewer then the main consequence is that it makes the point-to-point Measure option in the Viewer's 3D pointcloud mode unselectable. So if you do not need to measure between two or more points then the Viewer will still be usable when GLSL is disabled.

Disabling the two GLSL options can also resolve another known Viewer pointcloud issue where the pointcloud flickers and then disappears a few seconds after streaming is started.

[mkelrajt]

Hi @MartyG-RealSense thank you for your reply.
I was aware of the memory leak, but the debug assertion error is new.

[MartyG-RealSense]

As GLSL support has to be programmed into an application deliberately and is not enabled by default (GLSL is optional support for acceleration of certain RS2:: SDK functions, such as rs2::pointcloud and rs2::align) you should be able to use Debug mode with 2.50.0 if you do not use the rs-gl example program, do not use GLSL in your own programs or you disable GLSL in the Viewer.

[MartyG-RealSense]

Hi @mkelrajt Do you require further assistance with this case, please? Thanks!

[mkelrajt]

I have no further questions, if new issues arise I will open a new ticket. Thank you for your reply.

[MartyG-RealSense]

Thanks very much @mkelrajt for the update. As you do not require further assistance with this case, I will close it. Thanks again!