Regression: Blender Crashes On Scene Switch #111165
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#111165
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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: Linux-5.19.0-43-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01
Blender Version
Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash:
8bda729ef4dc
Worked: 3.1
Caused by
31b2b84b3c
Short description of error
Blender crashes when switching to a scene that has another scene as a background scene.
Exact steps for others to reproduce the error
Uploaded crash log.
From default scene:
Create a new scene (scene.001).
set the background scene in the newly created scene as scene (the original scene).
Create a newer scene (scene.002).
Set the background scene in the newly created scene (scene.002) as scene.001.
Switch back to scene (the original).
Link the lamp to scene.001.
Link the camera to scene.002.
Now on switching to scene.002 blender crashes.
I was able to reproduce every time. But after saving the file before step 8 I could not reproduce the crash, but there was a very noticeable hang up on performing step 8.
This triggered
BLI_assert(base_index >= 0)
inCC @mont29
Blender Crashes On Scene Switchto Regression: Blender Crashes On Scene SwitchCaused by
31b2b84b3c
, CC @SergeyI've fixed the issue in the main branch which is aimed to be Blender 4.0.
If we want to fix the issue for Blender 3.6 LTS things are a bit more complicated. The fix for 4.0 relies on quite big change related on the way how scene/collection hierarchy is tracked. It is not something that is easy/safe to port to 3.6.
What we can do is to tag all scenes for update of the base flags. It is most likely safe, but there might be something that I am missing. Also, not sure how we'll be able to evaluate the fix before landing it.
@lichtwerk Do you have suggestions here?
If we are risking other bugs sneaking in, my vote is for not backporting anything (but the tradeoff of having this bug in 3.6LTS vs. potential other bugs is something you can probably judge better than me in this case).
Not sure what you mean by "evaluating the fix before landing it"? You could create a fix in the 3.6-release branch, test locally if it fixes this bug, create a PR targeting that 3.6-release branch, use the bot to very it builds and passes all tests? But that of course does not cover running into "something that you are missing", for that having more tests in that area would help? (like I said, not exactly sure if this your question, does it?)
What I meant is: I can think of an alternative fix for the 3.6 branch which will be better isolated from other areas than to what any cherry-pick might bring up. If we decide lets implement this solution I'll surely test it locally, but testing by a single person always has a risk of missing some scenario where the new code introduces problem. For the regular releases this is why we have bcon3/bcon4, where we have enough community people to help us testing. I don't think anything like that exists for the LTS?
I can only think of making a PR targeting that 3.6-release branch, let the bot do builds and poke as many people as possible to test?
Other than that, we could only bring it into 3.6.3 as early as possible and hope for the best that enough folks use/test the buildbot (candidate) builds and report back if something comes up
Ok, created PR #111190.
OK, thx, if you've gotten enough satisfying feedback on #111190 you can add #111165 to #109399 (with the remark to use PR #111190)
@Omer-Almadani @iss Do you mind helping me verifying this bug is fixed in the build from https://builder.blender.org/download/patch/PR111190/ ? :)
Unfortunately it crahsed.
Stack trace seems to be same.
@iss How exactly do you link objects to scenes? Do you use drag-n-drop or something else?
I use operator
make_links_scene()
as described in report either from menu it works or with F3.Ah, I've missed that bit of information from the log. Didn't know this operator existed, so was linking via drag-n-drop in the outliner.
I'll commit fixe to the main branch, and prepare a separate PR for the 3.6 branch. Likely, this should be much simpler and safer fix, so perhaps we will be able to ignore the more obscure #111190 for the backport.
Yeah if you have a patch I can help test it no problem.
@Omer-Almadani I misunderstood the issue a bit, and fixed crash caused by manipulation via the outliner drag-n-drop. This is not something that is very safe to port to the LTS, but it is fixed in the main branch.
Then I've also fixed the "Link Objects to Scene" operator in the main branch, and a fix for it is scheduled for the next LTS update.
I think it is safer to not attempt to fix the crash via outliner manipulation: is higher risk, and usecase is unclear. If someone really stumbles into this and makes it a priority we have a patch for it.
And to be clear: in the main branch (planned for Blender 4.0) I've fixed both ways of crashing Blender.
So thanks for being available, but I don't really think extra testing of patches is needed. Just enjoy the latest builds from buildbot and the 3.6 LTS once that is updated next time! :)