Page MenuHome

Blender crashes when switching to add-on tab
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19

Blender Version
Broken: version: 2.83 (sub 9), branch: master, commit date: 2020-03-15 22:43, hash: rBf06a6e92bc5e
Worked: 2.82 official, 2.81 official, 2.80 official.

Short description of error
Blender crashes when I click on my add-on tab in the sidebar menu.

The add-on in question is "Grungit", my own, but I also got the same error with many other add-ons, including HardOps, BlenderGIS, MeshMachine, and Decal Machine. Sometimes Blender crashes as soon as I open certain files.

I included a stripped-down version of my add-on without any actual functionality, just the UI and the properties. It can be used to reproduce the bug with factory settings.

The following error is shown as soon as I enable the add-on, but it doesn't crash.

ERROR (rna.define): c:\b\win64_cmake_vs2017\win64_cmake_vs2017\blender.git\source\blender\makesrna\intern\rna_define.c:1840 RNA_def_property_enum_items: "GrungitProperties.quality", enum identifiers must not contain spaces.

When I switch to the "Grungit" tab in the tools panel, Blender immediately crashes.

Exact steps for others to reproduce the error
1- Start Blender (factory settings)
2- Install the downloaded zip and enable it.
3- From the tools (n) panel, select the "grungit" tab. Blender crashes immediately.

Event Timeline

Ankit Meel (ankitm) closed this task as Archived.EditedMar 17 2020, 9:51 AM
Ankit Meel (ankitm) claimed this task.
Ankit Meel (ankitm) edited projects, added Add-ons (Community); removed BF Blender.

All the addon maintainers should fix the error like https://developer.blender.org/rBAcc237ba4df1bd0ebacbb80086f0cd2f522df1688
Since they are not supplied by Blender as defaults, bugs should be posted to respective bug trackers. thanks for the report

Ankit Meel (ankitm) reopened this task as Needs Triage.Mar 18 2020, 1:05 PM

The error was caused by a bug in RNA which is fixed with rBdd416681fbb022. So using spaces in BPY enum identifiers should be fine again.
No need for the Add-on authors to take action. (Except if they already did, then they can revert the change, doh!).