bpy.ops.sequencer.rebuild_proxy() don't release memory #37043

New Issue

Gabriel Caraballo · 2013-10-11T14:34:17+02:00

Gabriel Caraballo commented

2013-10-11 14:34:17 +02:00

%%%--- Operating System, Graphics card ---
Ubuntu 12.04 - NVidia GForce

- Blender version with error, and version that worked ---

SVN r 60528

- Short description of error ---

Making "Rebuild Proxy and Timecode Indices" on a clip don't release the resources after process completion.
This prevent the building of several proxys on one session.

Closing Blender and re opening it releases the memory.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Load one clips on the sequencer, press "Rebuild Proxy and Timecode Indices", Blender memory usage increments, but don't decrement after process completion.
Repeat the process until Blender crash.%%%

%%%--- Operating System, Graphics card --- Ubuntu 12.04 - NVidia GForce - Blender version with error, and version that worked --- SVN r 60528 - Short description of error --- Making "Rebuild Proxy and Timecode Indices" on a clip don't release the resources after process completion. This prevent the building of several proxys on one session. Closing Blender and re opening it releases the memory. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Load one clips on the sequencer, press "Rebuild Proxy and Timecode Indices", Blender memory usage increments, but don't decrement after process completion. Repeat the process until Blender crash.%%%

Gabriel Caraballo commented

2013-10-11 14:34:17 +02:00

Changed status to: 'Open'

Bastien Montagne commented

2013-10-11 15:04:03 +02:00

%%%Will have a look at this one, it actually annoyed me too a few times…%%%

Bastien Montagne commented

2013-10-13 12:40:48 +02:00

%%%Well, I think it’s a question of caching… At least, this patch solves the issue with scene sequences: http://www.pasteall.org/46445/diff

Unfortunately, video proxy building uses a complete different code (in ImBuf) I’m not familiar with... :/

Another strange thing, MEM_get_memory_in_use() reports everything is freed, so I guess the remaining mem is not handled by our guarded allocator?%%%

%%%Well, I think it’s a question of caching… At least, this patch solves the issue with scene sequences: http://www.pasteall.org/46445/diff Unfortunately, video proxy building uses a complete different code (in ImBuf) I’m not familiar with... :/ Another strange thing, MEM_get_memory_in_use() reports everything is freed, so I guess the remaining mem is not handled by our guarded allocator?%%%

Bastien Montagne commented

2013-10-13 15:11:06 +02:00

%%%I confirmed we had the same issue with clip editor's proxy building as well, so I think the problem in mostly in imbuf code.

Assigning to Sergey, who’s the boss here.%%%

%%%I confirmed we had the same issue with clip editor's proxy building as well, so I think the problem in mostly in imbuf code. Assigning to Sergey, who’s the boss here.%%%

Sergey Sharybin commented

2013-10-14 17:57:20 +02:00

%%%Expect it to be fixed in svn r60749.

Thanks for the report, closing :)%%%

%%%Expect it to be fixed in svn r60749. Thanks for the report, closing :)%%%

Sergey Sharybin commented

2013-10-14 17:57:20 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2013-10-14 17:57:20 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

bpy.ops.sequencer.rebuild_proxy() don't release memory #37043