Blender crashing randomly when working with Blender Active Asset Type #88504
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#88504
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.18362-SP0 64 Bits
Graphics card: GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71
Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-05-19 23:27, hash:
blender/blender@47e88345a1
Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: blender/blender@5be9ef4177
Worked: (newest version of Blender that worked as expected)
Addon Information
Name: BlenderKit Online Asset Library (2, 93, 0)
Author: Vilem Duha, Petr Dlouhy
Short description of error
This situation made that after crash the add-on Blender Active Asset Type is turned off.
Some of changes on .blend file is not saved or broken.
In relation https://developer.blender.org/T88502
https://blender.community/c/rightclickselect/Xwhbbc/ Implement BlenderKit addon in the new Asset Browser
Exact steps for others to reproduce the error
I just adding more than 5 materials and 1st,2-3nd ok next crashin.. no important what type of material I selecting - it's happening when moving from lib preview to object.
After crash in B3.0.0 whole objects are collections.. no exist nothin more on outliner, on scene objects are normaly.
Added subscriber: @ManBlender
I noticed permament case when doing ctr+z
Material is not restored then as default colour from blender - just white.
more, the active_material_index lossing name in python array and this same on GUI library *just icon exist
exist some loop after search, and only event on mouse breaking this, soo the case that not crashin is coz mouse is moving
next problem is Out of memory if Duplicated linked scenes, then often problem with slots that not allowing use Cycles
I noticed that GUI for Online Asset is often diferent after restart blender.. don't know why and not understand the situation.
Sometimes are serial icons, sometimes is combolist..
Other problem.. showing or hide the panel where user seleccting material have quir event to work, eg. mouse must be moved or object must be clicked, before this list is not open and not listing the materials, user then waiting but nothing happeing. Then user trying with 'eye" icon on/off many times.. this made other bug that helping crash blender.
Added subscriber: @Blendify
Changed status from 'Needs Triage' to: 'Archived'
Hi, Blender Kit is maintained independently of Blender now, please report the bug here:
https://github.com/BlenderKit/blenderkit/issues
The developers should check the tickets here if are actual for problems, and solve not expect to copy tickets to github.. I hope soo.. this what they planing.
It would be easier on developers if users could verify there issue still stands. A lot of the issues that I closed were old and inactive for months so the report could have been resolved.
For a developer to single handedly verify this is asking a lot on the developer especially when there are 50 or so reports here.