Compositor memory allocation bug #43846

New Issue

Tim Lewis · 2015-03-01T10:07:48+01:00

Tim Lewis commented

2015-03-01 10:07:48 +01:00

System Information
Windows 7 Geforce GTX 690 x2
Linux Ubuntu 14.04 LTS Gallium 0.4 on AMD TURKS

Blender Version
Broken: 2.73a 2015-01-07 13:17 Hash b4d8fb5

Crash when interacting with or adding new compositor output

Load attached blend, go to node editor:compositor and attempt to add Composite node. This causes a crash to occur. On Linux (but not windows for me) this gives the following message:

Calloc returns null: len=1489754760 in CompositorOperation, total 1681186568
Writing: /tmp/ExoMinerKickstarterVideoPacked8EVERYTHINGREMOVEDFORBUGHUNT.crash.txt
Writing: /tmp/ExoMinerKickstarterVideoPacked8EVERYTHINGREMOVEDFORBUGHUNT.crash.txt
Segmentation fault (core dumped)

Blender 2.73 (sub 0), Commit date: 2015-01-20 18:16, Hash `bbf09d9`

bpy.ops.node.add_node(type="CompositorNodeComposite", use_transform=True) # Operator

backtrace

./blender(BLI_system_backtrace+0x30) [0x9537fb0]
./blender() [0x8b47f83]
./blender() [0x8b4816c]
[0xb7796400]
./blender(_ZN19CompositorOperation13executeRegionEP4rctij+0xcb) [0x8ff972b]
./blender(_ZN9CPUDevice7executeEP11WorkPackage+0x53) [0x9019883]
./blender(_ZN13WorkScheduler18thread_execute_cpuEPv+0x24) [0x8fc7954]
./blender() [0x954bf40]
/lib/i386-linux-gnu/libpthread.so.0(+0x6f70) [0xb7481f70]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e) [0xb728850e]

If I were to speculate, that looks like Blender's allocating an erroneously large amount of memory.

File attachment:
ExoMinerKickstarterVideoPacked8EVERYTHINGREMOVEDFORBUGHUNT.blend

**System Information** Windows 7 Geforce GTX 690 x2 Linux Ubuntu 14.04 LTS Gallium 0.4 on AMD TURKS **Blender Version** Broken: 2.73a 2015-01-07 13:17 Hash b4d8fb5 Crash when interacting with or adding new compositor output Load attached blend, go to node editor:compositor and attempt to add Composite node. This causes a crash to occur. On Linux (but not windows for me) this gives the following message: Calloc returns null: len=1489754760 in CompositorOperation, total 1681186568 Writing: /tmp/ExoMinerKickstarterVideoPacked8EVERYTHINGREMOVEDFORBUGHUNT.crash.txt Writing: /tmp/ExoMinerKickstarterVideoPacked8EVERYTHINGREMOVEDFORBUGHUNT.crash.txt Segmentation fault (core dumped) # Blender 2.73 (sub 0), Commit date: 2015-01-20 18:16, Hash bbf09d9 bpy.ops.node.add_node(type="CompositorNodeComposite", use_transform=True) # Operator # backtrace ./blender(BLI_system_backtrace+0x30) [0x9537fb0] ./blender() [0x8b47f83] ./blender() [0x8b4816c] [0xb7796400] ./blender(_ZN19CompositorOperation13executeRegionEP4rctij+0xcb) [0x8ff972b] ./blender(_ZN9CPUDevice7executeEP11WorkPackage+0x53) [0x9019883] ./blender(_ZN13WorkScheduler18thread_execute_cpuEPv+0x24) [0x8fc7954] ./blender() [0x954bf40] /lib/i386-linux-gnu/libpthread.so.0(+0x6f70) [0xb7481f70] /lib/i386-linux-gnu/libc.so.6(clone+0x5e) [0xb728850e] If I were to speculate, that looks like Blender's allocating an erroneously large amount of memory. File attachment: [ExoMinerKickstarterVideoPacked8EVERYTHINGREMOVEDFORBUGHUNT.blend](https://archive.blender.org/developer/F146489/ExoMinerKickstarterVideoPacked8EVERYTHINGREMOVEDFORBUGHUNT.blend)

Tim Lewis commented

2015-03-01 10:07:48 +01:00

Changed status to: 'Open'

Tim Lewis commented

2015-03-01 10:07:48 +01:00

Added subscriber: @TimLuther

Bastien Montagne commented

2015-03-01 10:15:12 +01:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2015-03-01 10:15:12 +01:00

Bastien Montagne self-assigned this 2015-03-01 10:15:12 +01:00

Bastien Montagne commented

2015-03-01 10:15:12 +01:00

You are running out of memory, which is far from surprising since you are rendering about 222 billions of pixels (yes, 19201080327.67*327.67 - your render precentage is set to 32767% ;) ).

You are running out of memory, which is far from surprising since you are rendering about 222 billions of pixels (yes, 1920*1080*327.67*327.67 - your render precentage is set to 32767% ;) ).

Tim Lewis commented

2015-03-01 10:27:34 +01:00

Lol, that'd explain it. Well, if there is a bug then perhaps it'd be the percentage maxing out to 0x7FFF, can't recall doing that.
Thanks for finding the problem so quickly :)

Lol, that'd explain it. Well, if there is a bug then perhaps it'd be the percentage maxing out to 0x7FFF, can't recall doing that. Thanks for finding the problem so quickly :)

Bastien Montagne commented

2015-03-01 10:49:24 +01:00

Yes, that percentage value is strange… But we’d need a way to reproduce that glitch, as usual, before accepting it as a bug ;)

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

Compositor memory allocation bug #43846

Blender 2.73 (sub 0), Commit date: 2015-01-20 18:16, Hash bbf09d9

backtrace

Blender 2.73 (sub 0), Commit date: 2015-01-20 18:16, Hash `bbf09d9`