Switching in and out of local view in rendered mode in Cycles can cause a crash in heavy scenes #91944
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#91944
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.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12
Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-03 23:31, hash:
272a38e0c2
Short description of error
Seems to happen with OptiX set in the System settings. Cuda is slower on my machine, but doesn't seem to crash.
Exact steps for others to reproduce the error
On a more powerful GPU it may not crash.
local_view_switch_crash.blend
Log:
local_view_switch_crash.crash.txt
Added subscriber: @MarcinTwarowski
Added subscriber: @mano-wii
Thanks for the report.
Did this problem happen in previous versions of Blender?
(I don't have an Nvidia GPU available to test, so if anyone else can confirm the issue I would appreciate it).
@mano-wii
Yes, it's the same in 2.93.4
blender_debug_output.txt
blender_system_info.txt
I forgot to pack the environment map. Updated the blend file.
I have impression that newest builds are more stable. Blender will still crash after I spam / button for 10-15 seconds in the test scene I uploaded. I am working on an even heavier scene right now which does crash more consistently when switching the views.
Seems to happen with OptiX set in the System settings. Cuda is slower on my machine, but doesn't seem to crash. I made another report where OptiX seems to cause a crash in rendered mode: #92816
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Needs User Info'
Can't reproduce this.
Please check if this happens with latest builds. If issue persists, check if this happens when you run Blender with blender_factory_startup.cmd file
@iss
Since blender_factory_startup.cmd resets "Cycles Render Devices" to "None", I had to switch to "Optix". I go to local view first. Spamming "/" key will eventually crash Blender. Here's a video:
Blender_crash.mp4
blender_debug_output.txt
blender_system_info.txt
Added subscriber: @rjg
I am checking latest and
886196b888
with NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 with no crash.Can you upload file C:\Users\TwaMa\AppData\Local\Temp\local_view_switch_crash.crash.txt ?
This could be specific to your hardware too, check if latest drivers do resolve this.
@rjg Can you check if you can rerpoduce?
@iss Sorry, I currently don't have time to look into this. I'm very busy with my thesis until the start of February.
Edit: If I get the chance, I will take a look. I cannot make any promises though.
I'm unable to reproduce a crash in a release build with the steps from the video so far. Tested on Windows with driver version 496.76 on a GeForce GTX 1080 Ti and commit
6b5e1cfaca
.Geforce Experience shows me that I have latest (game ready) driver which is 496.76. This crash happens only in Optix mode. Doesn't happen with CUDA.
Tested with
2fb8c6805a
:local_view_switch_crash.crash.txt
You checked using Optix?
@MarcinTwarowski Yes. Perhaps reproducing the crash requires very specific timing for when the switch from/to local view happens in relation to the OptiX viewport rendering?
@rjg
Hard to tell. How heavy the scene is probably matters too and 1080 ti is more powerful than mine 1080.
Changed status from 'Needs User Info' to: 'Needs Triage'
Don't have any good idea to check here really. Perhaps if you can run Blender with
-t 1
argument it may reveal thread race condition if no crash will happen, but doesn't seem like that would be the case.local_view_switch_crash.crash.txt
I don't know if I did it correctly. I made a .bat file like this:
I meant only
blender.exe -t 1
. I don't think our .cmd files do pass args to Blender.local_view_switch_crash.crash.txt
It took a lot longer with -t 1 but it eventually crashed.
Longer render time is expected. Don't have other ideas to check really. Maybe if you try to simplify file removing half of elements at a time, you could isolate issue to particular object. But that wouldn't probably help with me reproducing the bug...
If I remove objects crash doesn't happen. I already tried to make the scene as minimal a possible, but it needs to be heavy enough to crash. It seems to have improved since I reported it anyway, it's not a big deal.
Now I have some evidence that viewport overlays have something to do with the crash. In the video below I was spamming "/" button for a minute but it crashed only after I turned on the overlays.
local_view_switch_crash.crash.txt
local_view_with_overlays_crash.mp4
Added subscriber: @Raimund58
Can not reproduce.
NVIDIA GeForce GTX 1070/PCIe/SSE2
Studio driver 511.09
blender_system_info.txt
Added subscriber: @PratikPB2123
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs User Info'
Cannot repro in
eb3ff1d6f9
(possibly due to #94479}Cannot repro in 3.0.1 release candidate
9600f36cfc
either.In both cases, I had to reduce the geometry though (only have a 6GB 970m).
@MarcinTwarowski : can you check if this is still an issue in these fresh builds from https://builder.blender.org/download/daily/?
If so, I have added the
Unconfirmed
tag with the following consequences:@lichtwerk I wasn't able to reproduce the crash in
b47a1867e8
I guess you can close it then.
EDIT: It still crashes in: 3.0.1 Release Candidate, branch: master, commit date: 2022-01-17 12:07, hash:
9600f36cfc
Added subscribers: @pmoursnv, @Sergey, @brecht
Hm, so there is something in 3.1 that would be nice to have in 3.0.1 as well [though not entirely necessary].
@Sergey, @pmoursnv , @brecht: any ideas which commit could have fixed that?
If not, we just go with 3.1 and leave 3.0.1 as it is...
Sorry for the confusion, but after almost 2 minutes of spamming the / button I was able to crash Blender in 3.1 too.
blender_system_info.txt
blender_debug_output.txt
When I first reported this bug crash happened after couple clicks, now I have to spam the button for a minute or two. Probably not worth investigating, especially since others can't reproduce.
Something new happened while I was smashing the / button:
Materials didn't render on some of the objects. Again, not sure if worth investigating.
I have asked around in https://blender.chat/channel/blender-triagers to see if other people can repro this.
But since we've had no luck so far, it will stay
Unconfirmed
for nowMaybe it's just my graphics card slowly dying 🤷
Changed status from 'Needs User Info' to: 'Archived'
Since we seem to get stuck here (and this has been unconfirmed for quite a while now), will stick with the tracker policy and close.
(of course feel free to comment again if this can indeed be reproduced by someone else, we can always reopen in such case)