Blender crash when disabling BlenderKit addon while viewport is in "solid" shading mode #73467
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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-addons#73467
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?
(There are other bugs with BlenderKit that I'll report, but since this one crashes Blender, I assumed this is a Blender bug?)
System Information
Operating system: Linux-4.18.0-25-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116
Blender Version
Broken: version: 2.83 (sub 1), branch: master, commit date: 2020-01-28 16:02, hash:
blender/blender@a5790b2656
Short description of error
Blender crashes when enabling BlenderKit and then disabling it, e.g. if clicking a few times on the enable/disable checkbox
Exact steps for others to reproduce the error
Blender 2.83 (sub 1), Commit date: 2020-01-28 16:02, Hash a5790b26563c
bpy.data.window_managers["WinMan"].addon_search = "blenderkit" # Property
backtrace
/path/to/blender/blender-2.83-a5790b26563c-linux-glibc217-x86_64/blender(BLI_system_backtrace+0x1d) [0x6fc38ad]
/path/to/blender/blender-2.83-a5790b26563c-linux-glibc217-x86_64/blender() [0x16582a2]
/lib/x86_64-linux-gnu/libc.so.6(+0x41100) [0x7ff241d23100]
[0x7ff20ee48070]
Update: this seems to happen only in "solid" shading mode in the viewport. If I switch to e.g. Material Preview, the crash doesn't seem to happen.
Added subscriber: @clepsydrae
Blender crash when disabling BlenderKit addonto Blender crash when disabling BlenderKit addon while viewport is in "solid" shading modeAdded subscriber: @JulianEisel
Tried, but was not able to reproduce this, even with given commit. Even with ASan enabled, which should definitely cause a crash or warning on illegal memory usage.
I can't reproduce it on my other Linux system either (old/slow Lubuntu netbook) but it happens every time on my Kubuntu desktop... anything else I can do to help explore this?
I don't think this will help given what I've heard from devs, and I don't know anything about all this, but following some online instructions I went down this gdb hole, in case there are any clues in here somewhere: blenderkitcrash.txt
Added subscriber: @VilemDuha
I actually experienced this bug too and I hope I already fixed it in BlenderKit.
But it's actually some registration bug that is specific to Blender. I found out that it happens due to un-registation unregistering BlenderKit properties before unregistering the UI - then a menu draw call crashed Blender. Now I check in the ui draw code if the addon is registered - this hopefully fixed the problem.
Yeah, downloaded the latest (cad09e5227df) and no more crash! Thanks!
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
After 2 days of testing, I can now assume I fixed this bug successfully (committed to 2.82 master). If you experience it again, please reopen.
Changed status from 'Needs Developer To Reproduce' to: 'Resolved'