RTX 3080 GPU Memory Leak #90011

Closed
opened 2021-07-21 11:58:25 +02:00 by David Cherrie · 15 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41

Blender Version
Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: 1b8d33b18c
Worked: Definitely was working in 2.91, maybe 2.92.

Short description of error
Whilst rendering an animation, hundreds of frames in it will stop rendering with the error "System is out of GPU memory". Rendering each frame as an .png image.

Exact steps for others to reproduce the error
Render an animation in Cycles using GPU compute Optix. Am unsure if this issue is just to do with Optix or if it is isolated to Cycles and not Eevee. It's hard to test since it takes an hour or two for it to reach 150 frames. As I understand, the GPU memory shouldn't rollover between each frame. But currently I can't render animations over night because it stops after an hour.

I've only tried this with one complicated file. I don't really have time to do complicated trouble shooting and testing as each test takes hours to eventuate.

I've googled and saw there has been a few people have this exact same issue on the exact same card.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41 **Blender Version** Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: `1b8d33b18c` Worked: Definitely was working in 2.91, maybe 2.92. **Short description of error** Whilst rendering an animation, hundreds of frames in it will stop rendering with the error "System is out of GPU memory". Rendering each frame as an .png image. **Exact steps for others to reproduce the error** Render an animation in Cycles using GPU compute Optix. Am unsure if this issue is just to do with Optix or if it is isolated to Cycles and not Eevee. It's hard to test since it takes an hour or two for it to reach 150 frames. As I understand, the GPU memory shouldn't rollover between each frame. But currently I can't render animations over night because it stops after an hour. I've only tried this with one complicated file. I don't really have time to do complicated trouble shooting and testing as each test takes hours to eventuate. I've googled and saw there has been a few people have this exact same issue on the exact same card.
Author

Added subscriber: @davidcherrie

Added subscriber: @davidcherrie

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

Can you check if it is possible to render from point where it crashes? Just wanted to check if this is leak or there are frames where complexity causes out of memory situation.

Can you check if it is possible to render from point where it crashes? Just wanted to check if this is leak or there are frames where complexity causes out of memory situation.
Author

Yes I was able to re-render after starting the render again. First time it got to frame 155 and then continued on from that frame which it got to frame 206. I would have expected it to have rendered another 155 frames but it only rendered 51.

The scene I was rendering not much changes throughout the animation. It’s heavy on a particle system with a non-moving crowd which are Make Humans. The only things that are animated in the render is the movement of the camera and 2 faces of an object which have an image sequence playing on them as giant LED screens.

No physics simulations or volumetrics, may be complex to me but probably not to a movie project.

Yes I was able to re-render after starting the render again. First time it got to frame 155 and then continued on from that frame which it got to frame 206. I would have expected it to have rendered another 155 frames but it only rendered 51. The scene I was rendering not much changes throughout the animation. It’s heavy on a particle system with a non-moving crowd which are Make Humans. The only things that are animated in the render is the movement of the camera and 2 faces of an object which have an image sequence playing on them as giant LED screens. No physics simulations or volumetrics, may be complex to me but probably not to a movie project.

This could be a leak from what you say. Can you upload the file simplified as much as possible? Not sure how large the file is in terms of filesize. But if it's large and it would crash even with textures and caches stripped, that would be best.

This could be a leak from what you say. Can you upload the file simplified as much as possible? Not sure how large the file is in terms of filesize. But if it's large and it would crash even with textures and caches stripped, that would be best.
Author

I can't actually upload the file due to NDA. However working on another file (which I also can't share) which is totally seperate, after rendering multiple 4K images out over the course of working on the file for a few hours. I got the error message "System out of GPU memory". I escaped, didn't close the file but tried to re-render, same message came up and wouldn't start. I then went from LookDev to the internal shade view (forget what its called), pressed render then it started rendering.

I'll never render whilst looking in Render View in the viewport with cycles, as Blender 1 out of 3 times will either crash or also come up with "System out of GPU memory" but it seems that rendering in 4K especially when working in the document for several hours and rendering out lots of previews to see what it looks like, also results in the same issue that was made from a totally different project. So it's nothing specific with the files.

I have a few generic projects I can share which I was just playing around with. I'll do a test when I can to render an animation out of that and see if the issue occurs, then send the file to you.

I can't actually upload the file due to NDA. However working on another file (which I also can't share) which is totally seperate, after rendering multiple 4K images out over the course of working on the file for a few hours. I got the error message "System out of GPU memory". I escaped, didn't close the file but tried to re-render, same message came up and wouldn't start. I then went from LookDev to the internal shade view (forget what its called), pressed render then it started rendering. I'll never render whilst looking in Render View in the viewport with cycles, as Blender 1 out of 3 times will either crash or also come up with "System out of GPU memory" but it seems that rendering in 4K especially when working in the document for several hours and rendering out lots of previews to see what it looks like, also results in the same issue that was made from a totally different project. So it's nothing specific with the files. I have a few generic projects I can share which I was just playing around with. I'll do a test when I can to render an animation out of that and see if the issue occurs, then send the file to you.

Sorry I missed notification here. Regarding NDA's usually files can be simplified to extend where only few objects will be left and project contain no confidential material. Not sure if that is case here though. Having generic purpose built file is best.

Having said that, is there any update?

Sorry I missed notification here. Regarding NDA's usually files can be simplified to extend where only few objects will be left and project contain no confidential material. Not sure if that is case here though. Having generic purpose built file is best. Having said that, is there any update?
Author

I have been trying on a file that I am able to share but yesterday had it rendering for 6 hours using Cycles at 1920x1080 and got up to 590 frames with no issues.

Will keep an eye out and see if I come across it again and will try on the original file.

I have been trying on a file that I am able to share but yesterday had it rendering for 6 hours using Cycles at 1920x1080 and got up to 590 frames with no issues. Will keep an eye out and see if I come across it again and will try on the original file.
Author

I have isolated the issue to a linked geometry node. Got 23 frames rendered in the original problematic file before the System is out of GPU Memory. After stopping the render and trying to restart the render, on the first frame I get the GPU Memory message.

I've gone to the file that has the original geometry node and rendered that and it is absolutely fine and has been going for several hours. The files are pretty much the same except one has the original geometry node and the problematic file is linking to that node in the original file. The geometry node in question is a node I use for populating grandstands in my aquatic stadium I have built. Has a seat and combines it with a randomly selected human to sit down.

On Monday I'll try appending rather than linking the geometry node into the problematic project and see if that works. Then I can safely say its an issue to do with linking and not appending geometry nodes.

I have isolated the issue to a linked geometry node. Got 23 frames rendered in the original problematic file before the System is out of GPU Memory. After stopping the render and trying to restart the render, on the first frame I get the GPU Memory message. I've gone to the file that has the original geometry node and rendered that and it is absolutely fine and has been going for several hours. The files are pretty much the same except one has the original geometry node and the problematic file is linking to that node in the original file. The geometry node in question is a node I use for populating grandstands in my aquatic stadium I have built. Has a seat and combines it with a randomly selected human to sit down. On Monday I'll try appending rather than linking the geometry node into the problematic project and see if that works. Then I can safely say its an issue to do with linking and not appending geometry nodes.

@davidcherrie Hi, just wondering about status of this report, did you manage to identify the issue and can you share sample file?

@davidcherrie Hi, just wondering about status of this report, did you manage to identify the issue and can you share sample file?
Contributor

Added subscriber: @Raimund58

Added subscriber: @Raimund58
Contributor

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Contributor

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Author

In #90011#1235906, @iss wrote:
@davidcherrie Hi, just wondering about status of this report, did you manage to identify the issue and can you share sample file?

Sorry, this has come up in a new project. I believe its an issue with Optix and switching to CUDA in the same session seems to fix the problem. Switching back to Optix, in the same session, get the "System is out of GPU Memory" on first render. I can share this project with you.

> In #90011#1235906, @iss wrote: > @davidcherrie Hi, just wondering about status of this report, did you manage to identify the issue and can you share sample file? Sorry, this has come up in a new project. I believe its an issue with Optix and switching to CUDA in the same session seems to fix the problem. Switching back to Optix, in the same session, get the "System is out of GPU Memory" on first render. I can share this project with you.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#90011
No description provided.