Regression: Blender crash when moving camera immediately after opening the project (OPTIX) #103408
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#103408
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
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56
Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash:
55485cb379
Worked: 3.3, 3.3.1 (not tested with 3.3.2)
Caused by
0d73d5c1a2
Short description of error
Blender crash when moving camera immediately after opening the project (Cycles - OPTIX)
Exact steps for others to reproduce the error
file base da canc per prova blocco vuoto PROVA 2_test.blend
Added subscriber: @Michele-Moscon
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Needs User Info'
I believe in step 2 you meant Rendered mode?
I can't reproduce this issue. Loading kernels step took about minute or 2, but eventually it started working well. Can you check if letting it work for few minutes would resolve this?
Hi Richard.
In step 2 I meant to click here:
The problem occurs if the camera movement is performed immediately after opening the file. If the kernel starts loading please after the operation is finished try closing Blender and repeating the operations from step 1. This time at step 2 the render should start immediately.
Letting it work for a few minutes, like you suggested, doesn't fix the problem. And in any case, the rendering of this scene with the PCs I use takes a few moments (after the kernel has loaded the first time). Furthermore, the problem does not occur when opening the file in previous versions of Blender.
When the problem occurs Blender freezes (no longer responds) but does not close.
I tested on two different computers and both have the problem. One computer is the one described in the bug report, the other is a powerful workstation with Treadripper PRO, 64GB RAM, 2 x RTX 3090, 2 x RTX 3080 Ti.
Thank you.
I noticed that in the first post the editor had added the endnotes to the numbered list. Now I've re-edited the task correcting it: there are only 4 steps and the subsequent texts are notes.
Changed status from 'Needs User Info' to: 'Needs Triage'
Unfortunately I can't reproduce the issue still. Do both PCs have dual GPUs? I would check if rendering on single GPU would cause freeze in such case, but that's just wild guess.
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Confirmed'
I can confirm, cannot bisect this atm. (building without Optix -- but will try setting this up).
Blender crash when moving camera immediately after opening the project (OPTIX)to Regression: Blender crash when moving camera immediately after opening the project (OPTIX)Added subscriber: @pmoursnv
@pmoursnv : this broke between good
05bf5c4e0e
and bad50c7eb14f4
, I suspectc9eb583460
as the culprit commit (since disabling denoising seems to get rid of the freeze -- even though OSL is not used at all in this file...)Mind checking?
One PC has one GPU, the other has 4. Both have the problem.
Can't reproduce a freeze or crash with the provided steps, neither with ToT, nor 3.4.1 branch.
The aforementioned culprit commit is unlikely to be the problem, it only takes effect when OSL is enabled, otherwise behavior is unchanged (it's also not really related to denoising, only that changing the denoising setting after rendering was already started happened to force a kernel reload). There have been a lot of Cycles changes in the suspected range of commits though.
Added subscriber: @LukasStockner
I can reproduce this as well, but the required timing is very specific.
Also, I can reproduce it in
05bf5c4e0e
as well, so maybe something went wrong doring bisecting?Appears to be caused by
0d73d5c1a2
, makes a lot more sense since that change involves locks.Added subscriber: @Sergey
Thread A:
Thread B:
The problem appears to be that:
run_update_for_next_iteration
releases thescene->mutex
but continues to hold thedelayed_reset_.mutex
BlenderSession::synchronize
grabsscene->mutex
before callingSession::reset
delayed_reset_.mutex
which never gets released because A waits to getscene->mutex
back before releasing it, which B still holdsThe problem goes away if I just unlock
reset_lock
inrun_update_for_next_iteration
after theif (delayed_reset_.do_reset)
block, but I'm not sure if that's safe to do. I don't see further accesses to delayed reset stuff below that, but I'm not really sure what the sequence here is supposed to be. @Sergey, does that sound reasonable?Thx checking Lukas!
Also Patrick!
@LukasStockner, I think it is safe to release the
reset_lock
early on. I don't really see reason why we really need to hold it longer.This issue was referenced by
2895c67086
Changed status from 'Confirmed' to: 'Resolved'