Cycles; use of color ramp node in latest builds will always crash after save and reload. #40864
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#40864
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Changed status to: 'Open'
Added subscriber: @Ace_Dragon
Oops, I guess I forgot to add the file.
Cycles_texture.blend
Also, the first time it crashed on F12 rendering, I noticed it occurred right after the step that said 'computing shaders'.
Added subscriber: @ThomasDinges
No crash on Win 7 with
b5982f7
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?
I did not change anything, CMJ is set. Maybe another developer can reproduce it, it does not crash for me.
Added subscriber: @ideasman42
Also cant redo crash with a recent build
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.
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?
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.
Changed status from 'Open' to: 'Resolved'