Compositing large images crashes blender #43745

New Issue

Carlo Andreacchio · 2015-02-20T07:42:16+01:00

Carlo Andreacchio commented

2015-02-20 07:42:16 +01:00

System Information
Windows 7 x64 gtx 580

Blender Version
Broken:2967253

Short description of error
We have a project that we are trying to render out its approximately 8k by 18k pixels. Unfortunetly we are unable to upload our production blend file. I will try to create a test file later.

We get these errors with the render:

This one is in the console:
Malloc returns null: len=9676820784 in COM_MemoryBuffer, total 2799253272
Malloc returns null: len=2419205196 in COM_MemoryBuffer, total 2799253272
Malloc returns null: len=9676820784 in COM_MemoryBuffer, total 2799253272
Malloc returns null: len=9676820784 in COM_MemoryBuffer, total 2799253272
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 2799253272
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 2799253272
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900
Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900
Calloc returns null: len=2419426512 in CompositorOperation, total 3404109900
Calloc returns null: len=604856628 in CompositorOperation, total 3404109900

And then we get this one as a window:

"The instruction at 0x4009c213 referenced memory at 0x00000000. The memory could not be written.

Click on OK to terminate the program"

The amount of memory used before the compositing phase is approximately 5GB... we have 12GB in these machines.

**System Information** Windows 7 x64 gtx 580 **Blender Version** Broken:2967253 **Short description of error** We have a project that we are trying to render out its approximately 8k by 18k pixels. Unfortunetly we are unable to upload our production blend file. I will try to create a test file later. We get these errors with the render: This one is in the console: Malloc returns null: len=9676820784 in COM_MemoryBuffer, total 2799253272 Malloc returns null: len=2419205196 in COM_MemoryBuffer, total 2799253272 Malloc returns null: len=9676820784 in COM_MemoryBuffer, total 2799253272 Malloc returns null: len=9676820784 in COM_MemoryBuffer, total 2799253272 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 2799253272 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 2799253272 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=604856628 in COM_MemoryBuffer, total 3404109900 Malloc returns null: len=2419426512 in COM_MemoryBuffer, total 3404109900 Calloc returns null: len=2419426512 in CompositorOperation, total 3404109900 Calloc returns null: len=604856628 in CompositorOperation, total 3404109900 And then we get this one as a window: "The instruction at 0x4009c213 referenced memory at 0x00000000. The memory could not be written. Click on OK to terminate the program" The amount of memory used before the compositing phase is approximately 5GB... we have 12GB in these machines.

Carlo Andreacchio commented

2015-02-20 07:42:16 +01:00

Changed status to: 'Open'

Carlo Andreacchio commented

2015-02-20 07:42:16 +01:00

Added subscriber: @candreacchio

Thomas Dinges commented

2015-02-20 10:38:17 +01:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2015-02-20 10:38:17 +01:00

Without a test file, it's very difficult to know what's going on I am afraid. Will mark it as Incomplete for the time being.

Bastien Montagne commented

2015-02-20 10:42:08 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2015-02-20 10:42:09 +01:00

The code is trying to allocate giant chunks of memory (up to 9.6GB at once it seems!). Even if there were enough free mem (which is not the case here), fragmentation of mem would likely make such a call fail anyway.

Not sure why that happens though, 8k*18k picture should be about 2.3GB of mem in float RGBA? But hard to say more without a file to reproduce it for sure.

The code is trying to allocate giant chunks of memory (up to 9.6GB at once it seems!). Even if there were enough free mem (which is not the case here), fragmentation of mem would likely make such a call fail anyway. Not sure why that happens though, 8k*18k picture should be about 2.3GB of mem in float RGBA? But hard to say more without a file to reproduce it for sure.

Bastien Montagne commented

2015-02-27 12:17:25 +01:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2015-02-27 12:17:25 +01:00

Bastien Montagne self-assigned this 2015-02-27 12:17:25 +01:00

Bastien Montagne commented

2015-02-27 12:17:25 +01:00

No news since one week…

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

Compositing large images crashes blender #43745