CUDA memory leak #45131

New Issue

Andy Buchanan · 2015-06-21T01:56:22+02:00

Andy Buchanan commented

2015-06-21 01:56:22 +02:00

System Information
OS X 10.10.3 (14D136)
NVIDIA GeForce GTX 775M 2048MB
(Late 2013 27" iMac with latest released Yosemite)

CUDA Driver Version: 7.0.36
GPU Driver Version 10.2.7 310.41.25f01

Blender Version
2.75rc1 Date 2015-06-10 15:39 Hash: bff8b5d
Worked: Not sure, 2.71 maybe, it's been a bit flaky for a while.

GPU rendering appears to leak the CUDA memory such that extended operation is impossible without a reboot.

Execute normal model/light/material/render workflow. After a number of renders the GPU rendering will fail to operate with a CUDA out of memory error message.
Larger scenes exhaust memory quicker. Also using GPU rendering for render preview seems to be the worst possible option.

NOTE. After GPU rendering usage, with or without errors the rest of the OS X experiences some non-terminal graphical corruption, so probably the driver is at least partially implicated.

**System Information** OS X 10.10.3 (14D136) NVIDIA GeForce GTX 775M 2048MB (Late 2013 27" iMac with latest released Yosemite) CUDA Driver Version: 7.0.36 GPU Driver Version 10.2.7 310.41.25f01 **Blender Version** 2.75rc1 Date 2015-06-10 15:39 Hash: bff8b5d Worked: Not sure, 2.71 maybe, it's been a bit flaky for a while. GPU rendering appears to leak the CUDA memory such that extended operation is impossible without a reboot. Execute normal model/light/material/render workflow. After a number of renders the GPU rendering will fail to operate with a CUDA out of memory error message. Larger scenes exhaust memory quicker. Also using GPU rendering for render preview seems to be the worst possible option. NOTE. After GPU rendering usage, with or without errors the rest of the OS X experiences some non-terminal graphical corruption, so probably the driver is at least partially implicated.

Andy Buchanan commented

2015-06-21 01:56:22 +02:00

Changed status to: 'Open'

Andy Buchanan commented

2015-06-21 01:56:22 +02:00

Added subscriber: @JiggyWig

Sergey Sharybin commented

2015-06-22 14:18:15 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-06-22 14:18:15 +02:00

It's quite tricky to leak memory on CUDA, all memory is getting freed when CUDA context is being closed and CUDA context is forced to be closed when application quits.

So unless you can confirm that re-starting blender frees GPU memory it's likely to be a bug in the driver which we cant' really help with.

It's quite tricky to leak memory on CUDA, all memory is getting freed when CUDA context is being closed and CUDA context is forced to be closed when application quits. So unless you can confirm that re-starting blender frees GPU memory it's likely to be a bug in the driver which we cant' really help with.

Andy Buchanan commented

2015-06-22 21:09:50 +02:00

I put rc2 through its paces tonight for a couple of hours. So far I could not find a procedure to definitely leak CUDA memory, but getting anywhere near the limit ( around 1.1Gb on my 2Gb card. ) starts the video driver corruption problems. Additionally using gpu preview render near the memory limit produced two hard hangs requiring reboot, behaviour also seen on 2.74 but NOT 2.73a.

I'm sure you're right that it's probably the driver at fault. Alas, they don't seem to be in any hurry to update it again.

I put rc2 through its paces tonight for a couple of hours. So far I could not find a procedure to definitely leak CUDA memory, but getting anywhere near the limit ( around 1.1Gb on my 2Gb card. ) starts the video driver corruption problems. Additionally using gpu preview render near the memory limit produced two hard hangs requiring reboot, behaviour also seen on 2.74 but NOT 2.73a. I'm sure you're right that it's probably the driver at fault. Alas, they don't seem to be in any hurry to update it again.

Bastien Montagne commented

2015-06-30 23:00:02 +02:00

Added subscriber: @mont29