Blender permanently increases in memory usage with each render, when motion blur is enabled #48038

Closed
opened 2016-04-03 00:23:35 +02:00 by Mircea Kitsune · 8 comments

Blender permanently increases in RAM usage after each render, whenever motion blur is used. The memory leaks are very violent, and Blender can sometimes gain nearly 1GB of RAM per render! I believe I first noticed this in Blender 2.76, but it still exists in 2.77. I use the official x64 Linux build of Blender under openSUSE Tumbleweed. Currently I need to disable motion blur so I can render my animations altogether.

I'm noticing this in camera tracks rendered under Cycles: If on the Foreground render layer I enable the Vector pass, and under composite nodes I add a Vector Blur node, the problem begins to occur. To my surprise, I noticed this also happens if I don't enable the Vector pass or use a Vector Blur node, but simply enable the native Motion Blur in Cycles (the Motion Blur option in the Render panel). In one test case, this is with how much RAM the process increased every render:

Render #1: 1.589 MB
Render #2: 2.443 MB
Render #3: 3.302 MB

There's currently one important clue I was able to uncover: The aggressivity of the leaks seems to depend on the polygon count of objects in the scene. If I disable all Subsurf modifiers, the issue lessens and sometimes disappears entirely! For the test case above, this is how enabling Simplify and setting maximum subdivisions to 0 changed the leaks:

Render #1: 1.280 MB
Render #2: 1.903 MB
Render #3: 2.526 MB

As the projects I'm experiencing this in are large (eg: video backgrounds) and currently private, I can't produce a test case I can upload as easily. The problem should be easy for others to reproduce however, unless something very specific is somehow causing it on my system.

Blender permanently increases in RAM usage after each render, whenever motion blur is used. The memory leaks are very violent, and Blender can sometimes gain nearly 1GB of RAM per render! I believe I first noticed this in Blender 2.76, but it still exists in 2.77. I use the official x64 Linux build of Blender under openSUSE Tumbleweed. Currently I need to disable motion blur so I can render my animations altogether. I'm noticing this in camera tracks rendered under Cycles: If on the Foreground render layer I enable the Vector pass, and under composite nodes I add a Vector Blur node, the problem begins to occur. To my surprise, I noticed this also happens if I don't enable the Vector pass or use a Vector Blur node, but simply enable the native Motion Blur in Cycles (the Motion Blur option in the Render panel). In one test case, this is with how much RAM the process increased every render: Render #1: 1.589 MB Render #2: 2.443 MB Render #3: 3.302 MB There's currently one important clue I was able to uncover: The aggressivity of the leaks seems to depend on the polygon count of objects in the scene. If I disable all Subsurf modifiers, the issue lessens and sometimes disappears entirely! For the test case above, this is how enabling Simplify and setting maximum subdivisions to 0 changed the leaks: Render #1: 1.280 MB Render #2: 1.903 MB Render #3: 2.526 MB As the projects I'm experiencing this in are large (eg: video backgrounds) and currently private, I can't produce a test case I can upload as easily. The problem should be easy for others to reproduce however, unless something very specific is somehow causing it on my system.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @MirceaKitsune

Added subscriber: @MirceaKitsune

Added subscriber: @brecht

Added subscriber: @brecht

Please do always try to create a .blend file to reproduce the issue. If it is in fact easy to reproduce, it should be possible to demonstrate with a small .blend that has a couple of meshes with high subdivisions?

Please do always try to create a .blend file to reproduce the issue. If it is in fact easy to reproduce, it should be possible to demonstrate with a small .blend that has a couple of meshes with high subdivisions?
Author

This comment was removed by @MirceaKitsune

*This comment was removed by @MirceaKitsune*
Author

Very well. This was actually easier than I thought: A simple Suzanne head with a subsurf of 6 is enough to visibly trigger the problem. These are the results I'm getting with it:

Startup: 338.8 MB
Render #1: 616.8 MB
Render #2: 853.2 MB
Render #3: 1,167.6 MB
Render #4: 1,484.4 MB
Render #5: 1,800.0 MB

Since I don't seem to be able to attach files on the bug tracker, I uploaded it here: http://www.pasteall.org/blend/41287

Very well. This was actually easier than I thought: A simple Suzanne head with a subsurf of 6 is enough to visibly trigger the problem. These are the results I'm getting with it: Startup: 338.8 MB Render #1: 616.8 MB Render #2: 853.2 MB Render #3: 1,167.6 MB Render #4: 1,484.4 MB Render #5: 1,800.0 MB Since I don't seem to be able to attach files on the bug tracker, I uploaded it here: http://www.pasteall.org/blend/41287
Author

Today I tried to render my scenes with fresh Blender settings (new ~/.config/blender/2.77 directory). To my surprise, the issue went away entirely! Blender also uses a lot less memory at startup and while rendering now.

I can only conclude that a faulty addon was behind this. I had a few enabled by default, although they were only for import / export. In the future, I'll only enable IO scripts when I actually need them, as a precaution.

Today I tried to render my scenes with fresh Blender settings (new ~/.config/blender/2.77 directory). To my surprise, the issue went away entirely! Blender also uses a lot less memory at startup and while rendering now. I can only conclude that a faulty addon was behind this. I had a few enabled by default, although they were only for import / export. In the future, I'll only enable IO scripts when I actually need them, as a precaution.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Campbell Barton self-assigned this 2016-04-03 22:25:03 +02:00
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#48038
No description provided.