Memory not freed after several renders #56825

Closed
opened 4 years ago by Metal3d · 10 comments

System Information
Linux Fedora 28 x64

Nvidia 1060 (3Go)

Blender Version
blender-2.79-5c10c92b23c-linux-glibc224-x86_64

Short description of error
Repeating the same render grows memory and fill it until no render is possible, freezing computer.

Exact steps for others to reproduce the error
To check the problem, it's better to have a heavy scene to rendern for example using Adaptive subsurface (micro displacement) or hair. The first time I render the image is ok and fast, then I rerender the scene (modifying camera angle, for example) and rerender, then rerender, and so on... After a while, the render is very slow, and may fill the memory. If I stop blender, and reopen the scene, it's ok.

I must admit that I use Cycles with CUDA and not tried without GPU.

**System Information** Linux Fedora 28 x64 Nvidia 1060 (3Go) **Blender Version** blender-2.79-5c10c92b23c-linux-glibc224-x86_64 **Short description of error** Repeating the same render grows memory and fill it until no render is possible, freezing computer. **Exact steps for others to reproduce the error** To check the problem, it's better to have a heavy scene to rendern for example using Adaptive subsurface (micro displacement) or hair. The first time I render the image is ok and fast, then I rerender the scene (modifying camera angle, for example) and rerender, then rerender, and so on... After a while, the render is very slow, and may fill the memory. If I stop blender, and reopen the scene, it's ok. I must admit that I use Cycles with CUDA and not tried without GPU.
Poster

Added subscriber: @Metal3d

Added subscriber: @Metal3d
Poster

CUDA 9.1

CUDA 9.1
mont29 commented 4 years ago
Owner

Added subscriber: @mont29

Added subscriber: @mont29
mont29 commented 4 years ago
Owner

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Please follow our [submission template and guidelines](https:*developer.blender.org/maniphest/task/edit/form/1/), also read [these tips about bug reports](https:*wiki.blender.org/wiki/Process/Bug_Reports), and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, **small and simple** .blend and/or other files to do so if needed, etc.
Poster

The step is simple. Make a scene and rendre it several times. You should see that memory is not freed.

I will try to make a .blend file and memory capture to show you.

Note: the latest release doesn't start on my computer. I need to start latest build.

The step is simple. Make a scene and rendre it several times. You should see that memory is not freed. I will try to make a .blend file and memory capture to show you. Note: the latest release doesn't start on my computer. I need to start latest build.
Poster

Ok I can give you a simple .blend file and a log file where the date, nvidia-smi and "free -m" output is done. Each time I pressed F12 and the render is finished, I logged that output.

You can see that the "used" column grows up each time. This scene is simple so it grows up 200Mo approximativally. Certain scene append 500Mo, 1Go... to RAM. That means that I should stop blender and restart it to empty memory usage to be able to render again.

Is that sufficient ? I can use "ps" output to point blender binary if needed.

Zip file is here https://drive.google.com/file/d/1PMTGPDJW3yGhi1szPw9XbkDn_uqcjpo9/view?usp=sharing

Regards,

Ok I can give you a simple .blend file and a log file where the date, nvidia-smi and "free -m" output is done. Each time I pressed F12 and the render is finished, I logged that output. You can see that the "used" column grows up each time. This scene is simple so it grows up 200Mo approximativally. Certain scene append 500Mo, 1Go... to RAM. That means that I should stop blender and restart it to empty memory usage to be able to render again. Is that sufficient ? I can use "ps" output to point blender binary if needed. Zip file is here https://drive.google.com/file/d/1PMTGPDJW3yGhi1szPw9XbkDn_uqcjpo9/view?usp=sharing Regards,
YAFU commented 4 years ago

Added subscriber: @YAFU

Added subscriber: @YAFU
YAFU commented 4 years ago

Hi. I'm not a developer. Do you mean System RAM or vRAM?
If you refer to system RAM, the following problem has been solved only for Blender 2.79b. The problem still persists for 2.79 from master and 2.8:
https://developer.blender.org/T54287

If you are referring to vRAM, you should test with Blender factory settings without addons enabled.

Hi. I'm not a developer. Do you mean System RAM or vRAM? If you refer to system RAM, the following problem has been solved only for Blender 2.79b. The problem still persists for 2.79 from master and 2.8: https://developer.blender.org/T54287 If you are referring to vRAM, you should test with Blender factory settings without addons enabled.
Poster

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Metal3d closed this issue 4 years ago
Metal3d self-assigned this 4 years ago
Poster

@YAFU right, at the same time you answered I pointed my report to the issue you've pointed ;)

And that's right that given MALLOC_CONF can stop the problem for a time. So I can close that issue and follow the one you gave.

Thanks a lot for you help (and thanks to the community for Blender, using it since 1999 and impressed of what it is going do be)

@YAFU right, at the same time you answered I pointed my report to the issue you've pointed ;) And that's right that given MALLOC_CONF can stop the problem for a time. So I can close that issue and follow the one you gave. Thanks a lot for you help (and thanks to the community for Blender, using it since 1999 and impressed of what it is going do be)
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#56825
Loading…
There is no content yet.