# Memory Leak in vtkRenderWindow Render

**URL:** <https://discourse.vtk.org/t/memory-leak-in-vtkrenderwindow-render/15339>\
**Category:** Support\
**Created:** [March 5, 2025, 11:10am UTC](https://discourse.vtk.org/t/memory-leak-in-vtkrenderwindow-render/15339 "2025-03-05T11:10:32Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![mikewho](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/m/f1d935/32.png) [@mikewho](https://discourse.vtk.org/u/mikewho)\
**Post date:** [November 19, 2025, 5:19pm UTC](https://discourse.vtk.org/t/memory-leak-in-vtkrenderwindow-render/15339/21 "2025-11-19T17:19:09Z")

</div>

Nvidia has now managed to find a fix for the issue, but is only deploying it to future driver versions for limited application profiles.

---

<div class="post-metadata">

**Author:** ![jaswantp](https://discourse.vtk.org/user_avatar/discourse.vtk.org/jaswantp/32/10046_2.png) [@jaswantp](https://discourse.vtk.org/u/jaswantp)\
**Post date:** [November 19, 2025, 5:44pm UTC](https://discourse.vtk.org/t/memory-leak-in-vtkrenderwindow-render/15339/22 "2025-11-19T17:44:19Z")

</div>

Do you have a release note, or anything public that we can look at that describes it is fixed?

---

<div class="post-metadata">

**Author:** ![mikewho](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/m/f1d935/32.png) [@mikewho](https://discourse.vtk.org/u/mikewho)\
**Post date:** [November 19, 2025, 5:46pm UTC](https://discourse.vtk.org/t/memory-leak-in-vtkrenderwindow-render/15339/23 "2025-11-19T17:46:37Z")

</div>

Unfortunately not. They communicated this to me in the discussion for the bug I submitted, and asked for my application profiles to be able to apply this rule.

---

<div class="post-metadata">

**Author:** ![jaswantp](https://discourse.vtk.org/user_avatar/discourse.vtk.org/jaswantp/32/10046_2.png) [@jaswantp](https://discourse.vtk.org/u/jaswantp)\
**Post date:** [November 19, 2025, 5:51pm UTC](https://discourse.vtk.org/t/memory-leak-in-vtkrenderwindow-render/15339/24 "2025-11-19T17:51:36Z")

</div>

Okay. In case some one runs into this in the future, it would help if they knew the “application profile” you used and how to set it so they don’t have the problem. It would greatly benefit the VTK user community if you can add some more information on what helped resolve the problem and since which version.

---

<div class="post-metadata">

**Author:** ![mikewho](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/m/f1d935/32.png) [@mikewho](https://discourse.vtk.org/u/mikewho)\
**Post date:** [November 19, 2025, 6:02pm UTC](https://discourse.vtk.org/t/memory-leak-in-vtkrenderwindow-render/15339/25 "2025-11-19T18:02:16Z")

</div>

Here’s what I can provide:

Bug ID 5167511  
GPU: RTX A2000  
Bug discovered in driver version 572.60, not present in 553.35  
The fix will be in all future R580 driver releases according to Nvidia, but only for the applications I specified to them (executable names, DLL names, etc.). If other users encounter this issue and want their applications to have the fix, they will need to submit their application information to Nvidia as well.

[Previous page](https://discourse.vtk.org/t/memory-leak-in-vtkrenderwindow-render/15339.md?page=1)