Cycles HIP-RT Memory leak #120702

New Issue

Robin-Snyders · 2024-04-16T16:20:26+02:00

Robin-Snyders commented

2024-04-16 16:20:26 +02:00

System Information
Operating system: Windows 11
Graphics card: 7800XT

Blender Version
Broken: 4.1.0
Worked: Never (new graphics card)

Short description of error
When rendering animation using HIP and AMD GPU, after a certain amount of frames rendered (usually about 500) my VRAM is full. It's only starting at about 4Gb and build up overtime until VRAM is full and render crahes. I'm pretty sure it's because the render is not flushing VRAM between frames which seems to be a VRAM leak.

Exact steps for others to reproduce the error
Render a simple animation scene for the error to appear faster depending on your amount of VRAM this could take a while (about 500-600 frames for me)
Look at the VRAM usage and watch it grow until it's full and blender becomes unresponsive

Each task manager screenshots are spaced by a few minutes (frame render takes about 10secs)
PS : On the screenshots, in french "Mémoire du GPU dédiée" is VRAM usage

**System Information** Operating system: Windows 11 Graphics card: 7800XT **Blender Version** Broken: 4.1.0 Worked: Never (new graphics card) **Short description of error** When rendering animation using HIP and AMD GPU, after a certain amount of frames rendered (usually about 500) my VRAM is full. It's only starting at about 4Gb and build up overtime until VRAM is full and render crahes. I'm pretty sure it's because the render is not flushing VRAM between frames which seems to be a VRAM leak. **Exact steps for others to reproduce the error** Render a simple animation scene for the error to appear faster depending on your amount of VRAM this could take a while (about 500-600 frames for me) Look at the VRAM usage and watch it grow until it's full and blender becomes unresponsive Each task manager screenshots are spaced by a few minutes (frame render takes about 10secs) PS : On the screenshots, in french "Mémoire du GPU dédiée" is VRAM usage

Capture d'écran 2024-04-16 162708.png

73 KiB

7593_autosave.blend

1.7 MiB

Capture d'écran 2024-04-16 163008.png

80 KiB

Capture d'écran 2024-04-16 3.png

83 KiB

Robin-Snyders added the

labels 2024-04-16 16:20:26 +02:00

Alaska commented

2024-04-17 04:41:09 +02:00

I can reproduce the issue with the setup listed below.
I could only reproduce this issue when using HIP-RT. HIP seemed to be fine with no noticable increase in VRAM usage after 200 frames.

Testing can be sped up by reducing the sample count and render resolution, and turning off denoising. This issue plagues Blender 4.0.2 and 3.6.X as well meaning this issue has been present since the introduction of HIP-RT. I will mark as "high priority" due to it impacting all versions of Blender with this feature.

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: AMD Radeon RX 7800 XT ATI Technologies Inc. 4.6.0 Core Profile Context 24.2.1.240215
Blender version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270

I can reproduce the issue with the setup listed below. I could only reproduce this issue when using HIP-RT. HIP seemed to be fine with no noticable increase in VRAM usage after 200 frames. Testing can be sped up by reducing the sample count and render resolution, and turning off denoising. This issue plagues Blender 4.0.2 and 3.6.X as well meaning this issue has been present since the introduction of HIP-RT. I will mark as "high priority" due to it impacting all versions of Blender with this feature. **System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: AMD Radeon RX 7800 XT ATI Technologies Inc. 4.6.0 Core Profile Context 24.2.1.240215 Blender version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: `40a5e739e270`

👍 1

Alaska added

and removed