Crash when entering edit mode with a lot of meshes selected #71015

Closed
opened 2019-10-22 10:49:12 +02:00 by Francois Rimasson · 6 comments

System Information
Operating system: windows 7
Graphics card: GTX 1660

Blender Version latest 2.81 and 2.852

I select multiple meshes in the attached porte13.blend file and enter edit mode : crash in most cases

This crash dosen't happen with Blender 2.80

porte_v13.zip

**System Information** Operating system: windows 7 Graphics card: GTX 1660 **Blender Version** latest 2.81 and 2.852 I select multiple meshes in the attached porte13.blend file and enter edit mode : crash in most cases This crash dosen't happen with Blender 2.80 [porte_v13.zip](https://archive.blender.org/developer/F7847155/porte_v13.zip)

Added subscriber: @FrancoisRimasson

Added subscriber: @FrancoisRimasson
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Can confirm.

getting this on open

ERROR (bke.modifier): /blender/source/blender/blenkernel/intern/modifier.c:410 modifier_setError: Enable 'Auto Smooth' option in mesh settings

getting this on entering editmode

BLI_assert failed: /blender/source/blender/gpu/intern/gpu_element.c:197, GPU_indexbuf_set_tri_verts(), at '(elem + 1) * 3 <= builder->max_index_len'

checking...

Can confirm. getting this on open ``` ERROR (bke.modifier): /blender/source/blender/blenkernel/intern/modifier.c:410 modifier_setError: Enable 'Auto Smooth' option in mesh settings ``` getting this on entering editmode ``` BLI_assert failed: /blender/source/blender/gpu/intern/gpu_element.c:197, GPU_indexbuf_set_tri_verts(), at '(elem + 1) * 3 <= builder->max_index_len' ``` checking...
Member

There is something wrong with the material indices of some meshes.

You can run this script to correct this:

import bpy
for ob in bpy.data.objects:
    if ob.data is None or ob.type != 'MESH':
        continue
    not_valid = ob.data.validate_material_indices()
    if not_valid:
        print("mat indices not_valid ", ob.name)
    else:
        print("mat indices valid ", ob.name)

output will be [just the bad ones]:

mat indices valid  screw_Plate_01.000
mat indices not_valid  screw_Plate_01.001
mat indices not_valid  screw_Plate_01.003
mat indices not_valid  screw_Plate_01.005
mat indices not_valid  screw_Plate_01.008
mat indices not_valid  screw_Plate_01.009
mat indices valid  screw_Plate_01.012
mat indices not_valid  screw_Plate_01.013
mat indices not_valid  screw_Plate_01.014
mat indices not_valid  screw_Plate_01.015

Now the question is: how did we get here?
This might be because of a recent bug blender had about multiple materials...
(if this is the case then you should run that script and you should not any errors/crashes anymore)

If these errors show up again after you have cleaned the file, we would need to know which operations caused this to happen? Any idea?

There is something wrong with the material indices of some meshes. You can run this script to correct this: ``` import bpy for ob in bpy.data.objects: if ob.data is None or ob.type != 'MESH': continue not_valid = ob.data.validate_material_indices() if not_valid: print("mat indices not_valid ", ob.name) else: print("mat indices valid ", ob.name) ``` output will be [just the bad ones]: ``` mat indices valid screw_Plate_01.000 mat indices not_valid screw_Plate_01.001 mat indices not_valid screw_Plate_01.003 mat indices not_valid screw_Plate_01.005 mat indices not_valid screw_Plate_01.008 mat indices not_valid screw_Plate_01.009 mat indices valid screw_Plate_01.012 mat indices not_valid screw_Plate_01.013 mat indices not_valid screw_Plate_01.014 mat indices not_valid screw_Plate_01.015 ``` Now the question is: how did we get here? This might be because of a recent bug blender had about multiple materials... (if this is the case then you should run that script and you should not any errors/crashes anymore) If these errors show up **again** after you have cleaned the file, we would need to know which operations caused this to happen? Any idea?

This issue was referenced by 65b414cfb2

This issue was referenced by 65b414cfb291e8ae47e92ab1b101de3fa6d19704

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Brecht Van Lommel self-assigned this 2019-11-06 16:10:41 +01:00
Sign in to join this conversation.
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
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#71015
No description provided.