Page MenuHome

Blender memory leak
Closed, ArchivedPublic

Description

System Information
Operating system and graphics card
Win 7 Home Prem 64bit, dual core intel 2.1ghz
integrated intel HD graphics

Blender Version
Broken: Blender 2.69 r60995
Worked: Blender 2.68a r58537

Short description of error
I dont receive an error, I notice additional memory usage, higher cpu usage, and slower response from other apps when blender 2.69 is running, especially noticable after rendering even a simple node modified scene. This same performance was not observed when immediately tested in 2.68a. I had the rc1 and 2 for 269 but I did not use them on my active projects to prevent possible problems from destroying any advancements made in said projects. Even just opening there was a decrease performance with nothing loaded in a scene. Closing takes longer than previous versions.

Exact steps for others to reproduce the error
Did not need a specific file or setup. was present only in 269 and regardless of whether cycles or internal was used.

Event Timeline

Kevin Cagle (kevintampa5) raised the priority of this task from to 90.
Kevin Cagle (kevintampa5) updated the task description. (Show Details)
Kevin Cagle (kevintampa5) edited a custom field.

Am i correct to assume that the blender version you refer to are the official binaries form blender.org ?

Did you move or migrate any user settings or scripts from 2.68 to 2.69 ?

If you did does the behaviour also occur when you factory reset 2.69 preferences ?

There can be many factors involved here, so please give us very specific steps to redo this issue.

Like "load this .blend file, render, open notepad, notice typing is slow" (silly example but you get the point). If you are noticing more memory usage, explain exactly how you are measuring that. It might happen very commonly for you, but if this was an obvious issue it would have been reported already and so far other users seem to have not noticed this, so we need specific information steps.

Trying with a factory reset is also important as mentioned, it may be some addon or particular setting that is causing problems.

Brecht Van Lommel (brecht) lowered the priority of this task from 90 to 30.Nov 18 2013, 12:04 PM
Brecht Van Lommel (brecht) changed the task status from Unknown Status to Unknown Status.Nov 26 2013, 8:07 PM
Brecht Van Lommel (brecht) claimed this task.

No reply in 10 days, so closing report. I couldn't find anything unusual myself in some tests. I can reopen this if more information is provided.