Lights causes memory leak

[Josh]

It's a memory leak in Nvidia's driver. I just installed driver 560.70 and now I see the same behavior as @Dreikblack

[Josh]

I narrowed the problem down further.

Bindless textures have a huge memory leak in Nvidia's current drivers. Simply getting the bindless handle and making the texture resident causes memory to be allocated each frame, even when no camera is in use.

[Josh]

Specifically, it's the call to glMakeTextureHandleResidentARB that causes memory to continously leak.

[Josh]

Reported to Nvidia here:
https://developer.nvidia.com/bugs/4787960

[Josh]

Also tested on an AMD 6600, memory in task manager was stable at 135 mb.

[Josh]

Response from Nvidia:

Quote

 

Hi Josh,

Thanks for reaching out and sorry for delayed response , the ticket somehow slips from my view for days . The ticket is routed to our engineering team and we will give a check soon . Will keep you updated here .
Best,
Yuki

 

 

[Josh]

From Nvidia:

Quote

 

Hi Josh,

Our engineer was able to reproduce this on a Geforce 1080 . But no 'repro' on a GeForce 2070 . I checked a little bit of your Forum topic that there is no mention to it on 2070 , but you filed the ticket with 2070 . Can you please be more specific on if you see the issue on 2070 there ? Thanks .
Best,
Yuki

 

 

[Andy90]

I have a 3060 and have the same issue

[Dreikblack]

47 minutes ago, Josh said:

. Can you please be more specific on if you see the issue on 2070 there

Updated drivers on PC with RTX 2070 - issue is there

[Josh]

Information has been forwarded to Nvidia.

[Andy90]

any news on this topic ?

[Josh]

Yeah, they asked for source code and I just sent them the RenderTexture class source code. If that is not enough I will need to create a simpler app from scratch to produce the error.

[Yue]

On 8/5/2024 at 9:23 AM, Josh said:

So you are saying the increased memory that mysteriously appears on some machines is due to stack memory?

This code should be added to the main loop, but I don't think it explains the problem:

while (PeekEvent()) WaitEvent();

The memory was running very slowly, but by putting this in, it remains stable. 

 

 //Main loop
 while (window->GetClosed() == false and window->GetKeyDown(KEY_ESCAPE) == false)
 {
     GUI->Update();
     world->Update();
     world->Render(window->GetFrameBuffer());
     while (PeekEvent()) WaitEvent();
 }

 

[Yue]

 If I only create a camera and do not load the map, it remains stable both in the game and in the task manager.

[Yue]

 

aWhen I load the default map I have memory leaks, the windows task manager shows how the memory is going up, however I have started to remove elements from the scenery, and finally I have removed the models of the boxes and the default character, and the program is now stable.

[Yue]

 

This is out of control, almost a gigabyte in ram, and it keeps going up, very slowly but it keeps going up, try it for 30 minutes.

[Yue]

I have started another test, starting with this memory in use.  Back in 30 minutes.

A map is loaded that only contains the sky box by default.

[Josh]

Response from Nvidia:

Quote

 

Hi Josh ,

Sorry for keeping you waiting for our updates . Good news , the issue is root caused and fixed in house . The fix will aim a next new feature branch driver 565 series in next month soon . Please keep close attention to our driver release page . You are also welcome to comment here if you need help in confirming a fix version . Thanks again for reporting a bug ticket to us .

Best,
Yuki

 

This means that @Dreikblack identified and caused a major driver bug to be fixed by Nvidia. Great job!

[Yue]

[Dreikblack]

565.90 NVIDIA divers fixed this issue.