Page MenuHome
Create Task
Maniphest T40864

Cycles; use of color ramp node in latest builds will always crash after save and reload.
Closed, ResolvedPublic
Actions

Description

System Information
Win7 64 bit, Ivy Bridge i7 CPU, ATI 7xxx GPU, 16 gigs of RAM

Blender Version
Broken: bd777ff
Worked: 8cea610

Short description of error
A commit in the last week broke the color ramp node and it cannot be used anymore in current builds. Once the file is saved, then rendering will always crash Blender after the file is reloaded.

Exact steps for others to reproduce the error
Add a material with a color ramp node in Cycles, save, exit, load, switch to rendered view or press F12, watch Blender crash. Or just switch to rendered view with the provided .blend, if it doesn't crash at first, do the saving and loading step and it should do it then.

If anyone can look it, thanks.

Event Timeline

Adam Friesen (ace_dragon) created this task.Jun 29 2014, 2:29 AM
Adam Friesen (ace_dragon) raised the priority of this task from to 90.
Adam Friesen (ace_dragon) updated the task description. (Show Details)
Adam Friesen (ace_dragon) added projects: BF Blender, Cycles.
Adam Friesen (ace_dragon) edited a custom field.
Adam Friesen (ace_dragon) added a subscriber: Adam Friesen (ace_dragon).
Adam Friesen (ace_dragon) added a comment.Jun 29 2014, 2:46 AM

Oops, I guess I forgot to add the file.

Cycles_texture.blend428 KBDownload

Also, the first time it crashed on F12 rendering, I noticed it occurred right after the step that said 'computing shaders'.

Thomas Dinges (dingto) added a subscriber: Thomas Dinges (dingto).Jun 29 2014, 1:09 PM

No crash on Win 7 with b5982f7

Thomas Dinges (dingto) lowered the priority of this task from 90 to Normal.Jun 29 2014, 1:29 PM
Adam Friesen (ace_dragon) added a comment.Jun 29 2014, 8:20 PM

I opened my file in the latest buildbot build and it still crashes.

However, I just discovered that the crashing issue is specific to the Multi-Jitter sampler (can't produce it with Sobol). Did you change the sampler before rendering by any chance?

Thomas Dinges (dingto) added a comment.Jun 29 2014, 9:12 PM

I did not change anything, CMJ is set. Maybe another developer can reproduce it, it does not crash for me.

Campbell Barton (campbellbarton) added a subscriber: Campbell Barton (campbellbarton).Jun 30 2014, 9:31 AM

Also cant redo crash with a recent build

Campbell Barton (campbellbarton) edited projects, added BF Blender: Unconfirmed; removed BF Blender.Jul 2 2014, 4:18 AM

The issue reported can't be reproduced so far, and has been moved to the BF Blender: Unconfirmed project.
If 2 other people aren't able to redo the bug after 2 weeks, it will be closed.

We appreciate the effort that goes into making bug reports, but to be able to fix bugs we have to be able to redo them.
If there is anything you can provide to help others to reproduce the problem, be sure to include it.

Adam Friesen (ace_dragon) added a comment.Jul 9 2014, 8:27 PM

Well I just downloaded the July 9th Win64 bit build from the buildbot and any pre-existing scene that uses a color-ramp node anywhere will still crash on the computing shaders step when Multi-Jitter is selected.

DingTo; it may have not crashed for you because the file was just created on your machine, can you double-check with the latest build to see if it's still not reproduceable for you?

Adam Friesen (ace_dragon) added a comment.Jul 11 2014, 8:25 PM

It looks like rev. 5e216a6 fixed the crashing for me, the new July 11 build from the buildbot renders the material fine using Multi-Jitter.

The report can be closed now.

Thomas Dinges (dingto) changed the task status from Unknown Status to Resolved.Jul 11 2014, 10:29 PM
Thomas Dinges (dingto) claimed this task.