Blender crash on change workspace or switch to edit mode (corrupt mesh) #77309

Closed
opened 2020-06-03 16:23:26 +02:00 by Vladimir · 8 comments

System Information
Operating system: Linux 5.6.15
Graphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.0.7

Blender Version
Broken: 2.83 (last build on 3 jun), 2.90
Worked: I don't known

Short description of error

Crash on change Workspace (Layout) or switch to edit mode

Exact steps for others to reproduce the error

test-bug.blend

  1. Open attached file
  2. Select the Layout and then return again to workspace the Modeling - Blender is crash
  3. Go to workspace Modeling and select object Helper and then press Tab to switch edit mode - Blender is crash

Crash report: test-bug.crash.txt

**System Information** Operating system: Linux 5.6.15 Graphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.0.7 **Blender Version** Broken: 2.83 (last build on 3 jun), 2.90 Worked: I don't known **Short description of error** Crash on change Workspace (Layout) or switch to edit mode **Exact steps for others to reproduce the error** [test-bug.blend](https://archive.blender.org/developer/F8574360/test-bug.blend) 1) Open attached file 2) Select the Layout and then return again to workspace the Modeling - Blender is crash 3) Go to workspace Modeling and select object Helper and then press Tab to switch edit mode - Blender is crash Crash report: [test-bug.crash.txt](https://archive.blender.org/developer/F8574361/test-bug.crash.txt)
Author

Added subscriber: @Wovchick

Added subscriber: @Wovchick
Vladimir changed title from Blender crash on change workspace or change to edit mode to Blender crash on change workspace or switch to edit mode 2020-06-03 16:38:52 +02:00

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

The file has a corrupt selection history element index, can you provide steps to make another object that crashes as this file does?

The file has a corrupt selection history element index, can you provide steps to make another object that crashes as this file does?
Campbell Barton changed title from Blender crash on change workspace or switch to edit mode to Blender crash on change workspace or switch to edit mode (corrupt mesh) 2020-06-03 16:45:13 +02:00
Author

In #77309#943706, @ideasman42 wrote:
The file has a corrupt selection history element index, can you provide steps to make another object that crashes as this file does?

I can’t repeat it on new project but if I create new project then append object Helper from test-bug.blend (File->Append...) then Blender also crashes. This is file (test-bug.blend) was created in Blender 2.90

> In #77309#943706, @ideasman42 wrote: > The file has a corrupt selection history element index, can you provide steps to make another object that crashes as this file does? I can’t repeat it on new project but if I create new project then append object Helper from test-bug.blend (File->Append...) then Blender also crashes. This is file (test-bug.blend) was created in Blender 2.90

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Campbell Barton self-assigned this 2020-06-04 06:52:11 +02:00

Closing, can re-open if you manage to create a corrupt mesh from scratch.

Note that running bpy.context.object.data.validate() in the Python console will fix this for the current mesh.

Closing, can re-open if you manage to create a corrupt mesh from scratch. Note that running `bpy.context.object.data.validate()` in the Python console will fix this for the current mesh.
Author

In #77309#944243, @ideasman42 wrote:
Closing, can re-open if you manage to create a corrupt mesh from scratch.

Note that running bpy.context.object.data.validate() in the Python console will fix this for the current mesh.

Thank You! It helps me.

> In #77309#944243, @ideasman42 wrote: > Closing, can re-open if you manage to create a corrupt mesh from scratch. > > Note that running `bpy.context.object.data.validate()` in the Python console will fix this for the current mesh. Thank You! It helps me.
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
2 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#77309
No description provided.