Crash when using a mask as the factor input for a color combine (mix) node with render resolution at 100% #32141

New Issue

Luke S. · 2012-07-18T19:50:29+02:00

Luke S. commented

2012-07-18 19:50:29 +02:00

%%%First off, I attempted to submit this bug yesterday, but had some problems. My sincerest apologies if this suddenly shows up twice (though actually this one contains some newer findings, so this is the one to look at).

As the summary says, using a mask as the factor input for most operations in a "color mix" node will cause blender to crash, if the render resolution is set to 100% in the properties tab. The problematic operators are: subtract, divide, difference, darken, lighten, overlay, dodge, burn, hue, saturation, value, color, soft light, and linear light. I have included a sample .blend file to showcase the crash, as well as simple instructions for reproducing it (nothing to it really). This blend has a simple compositing setup, with a movie clip and mask as inputs, a color combine (mix) node, and composite output. The movie clip (a single .jpg file) has been packed into the blend.

How to crash blender in 5 easy steps.

Open the attached .blend file.
Hit F12 to render. This isn't really necessary, as the crash happens whether there is a rendered result or not.
Observe that using a "mix" operation with render "resolution" set to 99% works correctly.
Switch render resolution to 100%, and select any of the previously mentioned operations (subtract, divide, difference, darken, lighten, overlay, dodge, burn, hue, saturation, value, color, soft light, or linear light) from the mix node's dropdown menu.
See Blender crash.

I used a computer with Mac OSX 10.6.8, and Blender r48999, which I built on this computer. For further reference I have attached the "System Info" file generated by Blender. Also, when starting Blender from the command line to get a little extra info, it says that there is a "Bus error" maybe that helps?

Thank you for your time,

LswaN%%%

%%%First off, I attempted to submit this bug yesterday, but had some problems. My sincerest apologies if this suddenly shows up twice (though actually this one contains some newer findings, so this is the one to look at). As the summary says, using a mask as the factor input for most operations in a "color mix" node will cause blender to crash, if the render resolution is set to 100% in the properties tab. The problematic operators are: subtract, divide, difference, darken, lighten, overlay, dodge, burn, hue, saturation, value, color, soft light, and linear light. I have included a sample .blend file to showcase the crash, as well as simple instructions for reproducing it (nothing to it really). This blend has a simple compositing setup, with a movie clip and mask as inputs, a color combine (mix) node, and composite output. The movie clip (a single .jpg file) has been packed into the blend. ----------------------------------------------------------- How to crash blender in 5 easy steps. 1. Open the attached .blend file. 2. Hit F12 to render. This isn't really necessary, as the crash happens whether there is a rendered result or not. 3. Observe that using a "mix" operation with render "resolution" set to 99% works correctly. 4. Switch render resolution to 100%, and select any of the previously mentioned operations (subtract, divide, difference, darken, lighten, overlay, dodge, burn, hue, saturation, value, color, soft light, or linear light) from the mix node's dropdown menu. 5. See Blender crash. ----------------------------------------------------------- I used a computer with Mac OSX 10.6.8, and Blender r48999, which I built on this computer. For further reference I have attached the "System Info" file generated by Blender. Also, when starting Blender from the command line to get a little extra info, it says that there is a "Bus error" maybe that helps? Thank you for your time, - LswaN%%%

Luke S. commented

2012-07-18 19:50:29 +02:00

Changed status to: 'Open'

Jeroen Bakker commented

2012-07-19 19:30:41 +02:00

%%%Possible fix in revision 49069. Please re-check.

Regards,
Jeroen

r49069 | jbakker | 2012-07-19 19:28:37 +0200 (Thu, 19 Jul 2012) | 10 lines

Possible fix for [#32141] Crash when using a mask as the factor input
for a color combine (mix) node with render resolution at 100%

Seems to be that the MaskNode has been created as a complex node. But no
complex features were used. Converted the execute pixel to simple
execution. And it sees that the crash does not happen.

Not sure if it is the issue is solved. I am going to let the user retest
with this revision.%%%

%%%Possible fix in revision 49069. Please re-check. Regards, Jeroen -- r49069 | jbakker | 2012-07-19 19:28:37 +0200 (Thu, 19 Jul 2012) | 10 lines Possible fix for [#32141] Crash when using a mask as the factor input for a color combine (mix) node with render resolution at 100% Seems to be that the MaskNode has been created as a complex node. But no complex features were used. Converted the execute pixel to simple execution. And it sees that the crash does not happen. Not sure if it is the issue is solved. I am going to let the user retest with this revision.%%%

Luke S. commented

2012-07-19 21:13:47 +02:00

%%%This fix works beautifully for me, no crashes in either of the files I originally had troubles with. Thanks very much!%%%

Sergey Sharybin commented

2012-07-22 14:53:48 +02:00

%%%Would close the report due to issue is solved.%%%

Sergey Sharybin commented

2012-07-22 14:53:48 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2012-07-22 14:53:48 +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

Crash when using a mask as the factor input for a color combine (mix) node with render resolution at 100% #32141

Regards, Jeroen

Regards,
Jeroen