Various scenes crash on F12 rendering in newer builds of master. #56655
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#56655
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
Win10 64 bit; 32 gigs RAM; Ryzen 2700X CPU; Nvidia 1060 6 GB GPU.
Blender Version
Broken: Hash
8a3b548cb2
Worked: Hash
5078b9d2d0
(July 18)Short description of error
On newer builds, I'm finding it not possible to render some existing scenes in Cycles because they are crashing when the actual rendering starts. The stats will get stuck on calculating the normals and Blender will then close. This is with CPU rendering and the underlying cause seems to be random (but the scene will crash 100 percent of the time). Whether or not denoising is on has no impact.
Exact steps for others to reproduce the error
Download the .blend file and press F12 (this is a production file, use only for testing).
.blend
Cycles_test26.blend
Added subscriber: @Ace_Dragon
Added subscriber: @janb-1
I can confirm the crash on intel cpu with this one and on windows 8.1. There indeed a lot of known crashers in master. I know 550 bugs is a lot, but at least fixing all the bug reports about crash would make the user experience much better for buildbot users, while making a more stable base for 2.8 I feel.
Added subscriber: @brecht
Please leave triaging reports to developers, confirmed means a developer can reproduce the issue.
ok, sorry, thought it would help.
Added subscriber: @mont29
Can confirm the crash here with current master, happens at start of actual tiles rendering (i.e. after whole init processes, tessellation, BVH building etc.). Just set very small rendering size to avoid spending hours waiting in a debug build. ;)
QTCreator gives me following backtrace:
Changed status from 'Open' to: 'Resolved'
This seems to have gotten fixed at some point, maybe one of the BVH8 bugs.