Memory leak when rendering #32465

Closed
opened 2012-09-02 06:33:43 +02:00 by Rian Tut · 8 comments

%%%Sys: Ubuntu 12.04 - 64bit graphic card Nvidia GTX 460
Blender builds: multiple
When rendering, total memory on the header just keeps climbing until the sys is locked down. I've tried cycles, and internal; easiest is straight composite through the node editor with a movie clip input. Tried multiple builds from graphicall to buildbot and trunk all have the same problem. Windows builds work fine.
%%%

%%%Sys: Ubuntu 12.04 - 64bit graphic card Nvidia GTX 460 Blender builds: multiple When rendering, total memory on the header just keeps climbing until the sys is locked down. I've tried cycles, and internal; easiest is straight composite through the node editor with a movie clip input. Tried multiple builds from graphicall to buildbot and trunk all have the same problem. Windows builds work fine. %%%
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

%%%Ok, Today I tried to render the same file i was testing with linux on windows and had the same problem. File is a node editor composite with a large 400 mb AVCHD H.264 clip as the input.
Created a new file with the same general layout and same input file-- rendered fine and total mem didn't go above 230mb's.
However, after saving the file and closing blender --- restarted blender and rendered without changing anything mem went out of control.
Tried a third new file to confirm; allways worked until saving and quitting blender , saving file and reloading without quitting blender doesn't cause a problem either and just a note: changing the compute device or enabling OpenCL in the Node editor didn't seem to change anything. %%%

%%%Ok, Today I tried to render the same file i was testing with linux on windows and had the same problem. File is a node editor composite with a large 400 mb AVCHD H.264 clip as the input. Created a new file with the same general layout and same input file-- rendered fine and total mem didn't go above 230mb's. However, after saving the file and closing blender --- restarted blender and rendered without changing anything mem went out of control. Tried a third new file to confirm; allways worked until saving and quitting blender , saving file and reloading without quitting blender doesn't cause a problem either and just a note: changing the compute device or enabling OpenCL in the Node editor didn't seem to change anything. %%%

%%%Please provide a simple .blend file that we can use to redo the problem.%%%

%%%Please provide a simple .blend file that we can use to redo the problem.%%%

%%%Fixed issue with movie clip being cached when rendering animation, which wasn't intended.
Please try using blender svn rev50355 (or newer) and see if your issue is resolved (builds would be available at builder.blender.org).

If the issue would still exist for you, please provide all files needed to reproduce the issue and give exact steps of reproducing the issue.%%%

%%%Fixed issue with movie clip being cached when rendering animation, which wasn't intended. Please try using blender svn rev50355 (or newer) and see if your issue is resolved (builds would be available at builder.blender.org). If the issue would still exist for you, please provide all files needed to reproduce the issue and give exact steps of reproducing the issue.%%%
Author

%%%Attached the file and the video clip. Created the file and tested on windows 7 64bit although linux is same.
1 open file 2 select the attached clip in node input hit render animation and observe the total mem on the header 3 save file and quit blender; reopen and observe the mem.
4 create new file and observe mem repeat step 3.
%%%

%%%Attached the file and the video clip. Created the file and tested on windows 7 64bit although linux is same. 1 open file 2 select the attached clip in node input hit render animation and observe the total mem on the header 3 save file and quit blender; reopen and observe the mem. 4 create new file and observe mem repeat step 3. %%%
Author

%%%Nice! problem gone.
thanks%%%

%%%Nice! problem gone. thanks%%%

%%%Cool to hear this!
Thanks for the report, closing it now.%%%

%%%Cool to hear this! Thanks for the report, closing it now.%%%

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
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#32465
No description provided.