Memory leakage in Sequencer #45570

New Issue

Real Name · 2015-07-27T04:45:18+02:00

Real Name commented

2015-07-27 04:45:18 +02:00

System Information
Windows 7, GeForce

Blender Version
2.74a 64 bit, hash: c27589e

Short description of error
Blender memory consumption is not limited during playback in Sequencer or rendering using Sequencer.

Exact steps for others to reproduce the error
Sorry for not applying a .blend file, but I think that it is not hard to reproduce.

I'm doing a video montage in Sequencer using a lot of video strips, some of them, of course, are just different cutted versions of one video file. The whole animation is about an hour long.

When I try to render my file the Blender crashes after consuming all of available memory. So I can render only ~5 minutes of my project at a time.

Also, there's the button in Sequencer named 'Refresh Sequencer', when I press it, sometimes the memory usage drops down to ~200 MB and sometimes Blender immediately crushes.

I have noticed that the most consuming case is when you have many frequently changing video strips.

Out of memory case log:

  Calloc returns null: len=8294400 in imb_addrectImBuf, total 1360638192
  Error: EXCEPTION_ACCESS_VIOLATION

'Refresh Sequencer' crash log:

  WM_operator_last_properties_init: loading previous properties for 'SEQUENCER_OT_refresh_all'
  ...
     READ: strID=1 (VID: 0) dts=55951360 pts=55951360  KEY
     READ: strID=1 (VID: 0) dts=55952384 pts=55952384  KEY
     READ: strID=1 (VID: 0) dts=55953408 pts=55953408  KEY

 - >READ: strID=0 (VID: 0) dts=38063025 pts=38064026  KEY

  ... (and many more READs)

Sorry for not debugging it, I'll try to provide any possible information you ask.

Memory disparity image:
http:*i.imgur.com/kb7Ff5t.png

MP4 files used:

  Stream #0:0(eng), 15, 1/30000: Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080, 1/60000, 20304 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 60k tbc (default)
  Stream #0:1(eng), 1, 1/44100: Audio: aac (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 125 kb/s (default)

**System Information** Windows 7, GeForce **Blender Version** 2.74a 64 bit, hash: c27589e **Short description of error** Blender memory consumption is not limited during playback in Sequencer or rendering using Sequencer. **Exact steps for others to reproduce the error** Sorry for not applying a .blend file, but I think that it is not hard to reproduce. I'm doing a video montage in Sequencer using a lot of video strips, some of them, of course, are just different cutted versions of one video file. The whole animation is about an hour long. When I try to render my file the Blender crashes after consuming all of available memory. So I can render only ~5 minutes of my project at a time. Also, there's the button in Sequencer named 'Refresh Sequencer', when I press it, sometimes the memory usage drops down to ~200 MB and sometimes Blender immediately crushes. I have noticed that the most consuming case is when you have many frequently changing video strips. ------------ Out of memory case log: ``` Calloc returns null: len=8294400 in imb_addrectImBuf, total 1360638192 Error: EXCEPTION_ACCESS_VIOLATION ``` 'Refresh Sequencer' crash log: ``` WM_operator_last_properties_init: loading previous properties for 'SEQUENCER_OT_refresh_all' ... READ: strID=1 (VID: 0) dts=55951360 pts=55951360 KEY READ: strID=1 (VID: 0) dts=55952384 pts=55952384 KEY READ: strID=1 (VID: 0) dts=55953408 pts=55953408 KEY ``` - >READ: strID=0 (VID: 0) dts=38063025 pts=38064026 KEY ``` ... (and many more READs) ``` Sorry for not debugging it, I'll try to provide any possible information you ask. ----------- Memory disparity image: [http:*i.imgur.com/kb7Ff5t.png](http:*i.imgur.com/kb7Ff5t.png) ----------- MP4 files used: ``` Stream #0:0(eng), 15, 1/30000: Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080, 1/60000, 20304 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 60k tbc (default) Stream #0:1(eng), 1, 1/44100: Audio: aac (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 125 kb/s (default)

Real Name commented

2015-07-27 04:45:18 +02:00

Changed status to: 'Open'

Real Name commented

2015-07-27 04:45:18 +02:00

Added subscriber: @uvx3

Aaron Carlisle commented

2015-07-27 17:11:35 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2015-07-27 17:11:35 +02:00

Also after rendering I have had a problem were memory is not freed afterwards

Sergey Sharybin commented

2015-07-28 12:24:33 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-07-28 12:24:33 +02:00

It is important to attach all files needed to reproduce the issue. Something which sounds obvious to you is not obvious for everyone. We're using sequencer on a daily basis here in the studio for Gooseberry edit and don't have memory leaks detected so far.

As for the crashes -- it'll help if you can isolate it a bit more. Crashes which happens sometimes to you are areally tricky to nail down from our side.

It is important to attach all files needed to reproduce the issue. Something which sounds obvious to you is not obvious for everyone. We're using sequencer on a daily basis here in the studio for Gooseberry edit and don't have memory leaks detected so far. As for the crashes -- it'll help if you can isolate it a bit more. Crashes which happens sometimes to you are areally tricky to nail down from our side.

Real Name commented

2015-07-28 17:50:16 +02:00

I've created a .blend file, which can help detect the error, I hope. It's in attached .7z archive. There's also some gdb output.

Thank you.

mem_leak.7z

I've created a .blend file, which can help detect the error, I hope. It's in attached .7z archive. There's also some gdb output. Thank you. [mem_leak.7z](https://archive.blender.org/developer/F214538/mem_leak.7z)

Sergey Sharybin commented

2015-07-28 18:37:38 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2015-07-28 18:37:38 +02:00

Sergey Sharybin self-assigned this 2015-07-28 18:37:38 +02:00

Sergey Sharybin commented

2015-07-28 18:37:38 +02:00

Refresh Sequencer is not really thread-safe button, better not be used during rendering. Committed change which makes sure it's not used during rendering.

As for memory usage -- the memory is being used by FFmpeg context associated with each of the strip. It's possible to make them better memory managed by blender, but for now it's considered a TODO: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Editors#Video_Sequencer

So thanks for the report, but archiving it as a TODO now.

Refresh Sequencer is not really thread-safe button, better not be used during rendering. Committed change which makes sure it's not used during rendering. As for memory usage -- the memory is being used by FFmpeg context associated with each of the strip. It's possible to make them better memory managed by blender, but for now it's considered a TODO: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Editors#Video_Sequencer So thanks for the report, but archiving it as a TODO now.

Real Name commented

2015-07-28 19:05:21 +02:00

Sergey, thank you for making Blender :)

Maybe you can advise me some sort of solution to render my project? Now I render it by 3—5 minutes long pieces only. Is there some kind of 'pause render' possibility to safely free the memory during rendering?

Sergey, thank you for making Blender :) Maybe you can advise me some sort of solution to render my project? Now I render it by 3—5 minutes long pieces only. Is there some kind of 'pause render' possibility to safely free the memory during rendering?

Sergey Sharybin commented

2015-07-28 19:19:22 +02:00

You can have a script which modifies render range, invokes animation rendering for a shorter frame range, then clears the cache and continues rendering.

Second idea is to have pre-render hook which will free cache as well, but this wouldn't work in the current Git version because of the thread safety check added recently. Would need to re-consider the fix to keep that usecase working..

You can have a script which modifies render range, invokes animation rendering for a shorter frame range, then clears the cache and continues rendering. Second idea is to have pre-render hook which will free cache as well, but this wouldn't work in the current Git version because of the thread safety check added recently. Would need to re-consider the fix to keep that usecase working..

Real Name commented

2015-07-28 19:28:38 +02:00

Ok, thank you.

Sybren A. Stüvel referenced this issue

2023-03-30 15:30:10 +02:00

Blender development todo list -- Editors #55366

Sign in to join this conversation.