Crashes on first click on model #65420

New Issue

Chris Wedgwood · 2019-06-02T17:04:18+02:00

Chris Wedgwood commented

2019-06-02 17:04:18 +02:00

Blender Version
Broken: 2019-06-01 22:51 079c7f918c

Exact steps for others to reproduce the error

Select Cube, go to Edit mode
Change the active object - open a Python console editor: C.view_layer.objects.active = D.objects['Camera']
Save and re-open file
Click on the cube

Simplified file (just open and select the cube):

crash-on-select-simple.blend

Original Report
K8_LOD0.blend

Click on arm. blender crashes to desktop.

**Blender Version** Broken: 2019-06-01 22:51 079c7f918c81 **Exact steps for others to reproduce the error** * Select Cube, go to Edit mode * Change the active object - open a Python console editor: `C.view_layer.objects.active = D.objects['Camera']` * Save and re-open file * Click on the cube Simplified file (just open and select the cube): [crash-on-select-simple.blend](https://archive.blender.org/developer/F7092529/crash-on-select-simple.blend) **Original Report** [K8_LOD0.blend](https://archive.blender.org/developer/F7084012/K8_LOD0.blend) Click on arm. blender crashes to desktop.

Chris Wedgwood commented

2019-06-02 17:04:19 +02:00

Added subscriber: @OXO

matc commented

2019-06-02 20:14:42 +02:00

Added subscriber: @matc

matc commented

2019-06-02 20:14:42 +02:00

Crash happens in stats_object_edit(Object *obedit, SceneStats *stats) where BKE_editmesh_from_object(obedit) returns NULL. Selecting "StickHandRD" in the Outliner has the same effect.

Selecting another Object ("SickLU") and switching to edit mode causes a crash in undomesh_from_editmesh where the edit mesh is NULL for "StickHandRD".

From the Data API it looks like "StickHandRD" is already in edit mode, without being selected. This is the only difference between "StickHandRD" and "StickHandLD" that I was able to spot (both have the same number of vertices etc.).
K8_LOD0.blend

Crash happens in `stats_object_edit(Object *obedit, SceneStats *stats)` where `BKE_editmesh_from_object(obedit)` returns NULL. Selecting "StickHandRD" in the Outliner has the same effect. Selecting another Object ("SickLU") and switching to edit mode causes a crash in `undomesh_from_editmesh` where the edit mesh is NULL for "StickHandRD". From the Data API it looks like "StickHandRD" is already in edit mode, without being selected. This is the only difference between "StickHandRD" and "StickHandLD" that I was able to spot (both have the same number of vertices etc.). [K8_LOD0.blend](https://archive.blender.org/developer/F7084012/K8_LOD0.blend)

Chris Wedgwood commented

2019-06-06 09:10:27 +02:00

I should like to escalate this one because its preventing me from continuing with testing 2.8

Brecht Van Lommel commented

2019-06-06 12:47:39 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-06-06 12:47:39 +02:00

We define the priority.

Dalai Felinto was assigned by Brecht Van Lommel

2019-06-06 12:48:08 +02:00

Brecht Van Lommel commented

2019-06-06 12:49:49 +02:00

@matc normally when we developers set a bug to confirm, it should be assigned to a developer immediately. Otherwise it's looks as if it's been triaged but none of the developers have assessed what kind of priority it has and who should look into it. If you don't know who to assign it to, just leave as Needs Triage.

Brecht Van Lommel commented

2019-06-06 13:05:41 +02:00

This may be related to #62450 (Undo crash after hiding object in edit mode) in some way.

Dalai Felinto commented

2019-06-07 17:21:05 +02:00

The issue on stat info, looking into it.

//source/blender/editors/space_info/info_stats.c:212:25: runtime error: member access within null pointer of type 'struct BMEditMesh'
Full backtrace: P999

The issue on stat info, looking into it. `//source/blender/editors/space_info/info_stats.c:212:25: runtime error: member access within null pointer of type 'struct BMEditMesh'` Full backtrace: [P999](https://archive.blender.org/developer/P999.txt)

Dalai Felinto commented

2019-06-07 17:50:45 +02:00

Added subscribers: @ideasman42, @dfelinto

Dalai Felinto removed their assignment 2019-06-07 17:50:45 +02:00

Campbell Barton was assigned by Dalai Felinto

2019-06-07 17:50:45 +02:00

Dalai Felinto commented

2019-06-07 17:50:45 +02:00

@OXO do you have instructions on how to reproduce this from scratch? Or any clues on which steps you did, what you were trying?

The issue here is that after selecting the object it becomes active, but for some reason the object is in edit mode ((ob)->mode & OB_MODE_EDIT) yet BKE_editmesh_from_object( ) returns NULL.

@ideasman42 you may want to take a look at this?

And even if we were to ignore this will break later down the line for the same reason.
And for the records, it was not introduced on db67a17d17.

@OXO do you have instructions on how to reproduce this from scratch? Or any clues on which steps you did, what you were trying? The issue here is that after selecting the object it becomes active, but for some reason the object is in edit mode ((ob)->mode & OB_MODE_EDIT) yet BKE_editmesh_from_object( ) returns NULL. @ideasman42 you may want to take a look at this? And even if we were to ignore this will break later down the line for the same reason. And for the records, it was not introduced on db67a17d17e39905271fe09d7814b028db9aef38.

Dalai Felinto commented

2019-06-07 17:51:31 +02:00

And slightly simplified file:
crash-select.blend

(removed the other objects and the other view layers)

And slightly simplified file: [crash-select.blend](https://archive.blender.org/developer/F7092205/crash-select.blend) (removed the other objects and the other view layers)

Chris Wedgwood commented

2019-06-07 18:07:57 +02:00

I can't say what caused this. The model was originally a wings3d file, which was imported to blender via wavefront obj import.

Then later another obj import with the offending Arm part was done.

I then worked on the modelling for some days, and out of the blue after duplicating the arm, it showed this issue.

I can't say what caused this. The model was originally a wings3d file, which was imported to blender via wavefront obj import. Then later another obj import with the offending Arm part was done. I then worked on the modelling for some days, and out of the blue after duplicating the arm, it showed this issue.

Campbell Barton was unassigned by Dalai Felinto

2019-06-07 20:53:37 +02:00

Dalai Felinto self-assigned this 2019-06-07 20:53:37 +02:00

Dalai Felinto commented

2019-06-07 20:53:37 +02:00

Alright, managed to reproduce from scratch:

Select Cube, go to Edit mode
Change the active object - open a Python console editor: C.view_layer.objects.active = D.objects['Camera']
Save and re-open file
Click on the cube

Simplified file (just open and select the cube):

crash-on-select-simple.blend

The issue is that ED_editors_init() doesn't initialize the object, nor clear its ob->mode flag (to remove OB_MODE_EDIT).

Alright, managed to reproduce from scratch: * Select Cube, go to Edit mode * Change the active object - open a Python console editor: `C.view_layer.objects.active = D.objects['Camera']` * Save and re-open file * Click on the cube Simplified file (just open and select the cube): [crash-on-select-simple.blend](https://archive.blender.org/developer/F7092529/crash-on-select-simple.blend) The issue is that *ED_editors_init()* doesn't initialize the object, nor clear its ob->mode flag (to remove OB_MODE_EDIT).

blender-admin commented

2019-06-07 22:15:52 +02:00

This issue was referenced by 6a15564682

This issue was referenced by 6a155646823024569c129e8bdcb55fb2de9b958e

Dalai Felinto commented

2019-06-08 00:18:03 +02:00

Changed status from 'Open' to: 'Resolved'

Dalai Felinto closed this issue

2019-06-08 00:18:03 +02:00

matc commented

2019-06-10 21:53:45 +02:00

In #65420#696183, @brecht wrote:
@matc normally when we developers set a bug to confirm, it should be assigned to a developer immediately. Otherwise it's looks as if it's been triaged but none of the developers have assessed what kind of priority it has and who should look into it. If you don't know who to assign it to, just leave as Needs Triage.

I think https://wiki.blender.org/wiki/Process/Help_Triaging_Bugs should be more clear about that.

Needs Triage by Developer

...

If you can reproduce the bug in the newest version, set the priority to Confirmed, Medium (a developer can change it to Low or High later on if appropriate).

> In #65420#696183, @brecht wrote: > @matc normally when we developers set a bug to confirm, it should be assigned to a developer immediately. Otherwise it's looks as if it's been triaged but none of the developers have assessed what kind of priority it has and who should look into it. If you don't know who to assign it to, just leave as Needs Triage. I think https://wiki.blender.org/wiki/Process/Help_Triaging_Bugs should be more clear about that. > **Needs Triage by Developer** > - ... > - If you can reproduce the bug in the newest version, set the priority to Confirmed, Medium (a developer can change it to Low or High later on if appropriate).

Brecht Van Lommel commented

2019-06-10 23:49:54 +02:00

Thanks for pointing that out, I've updated the page now.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crashes on first click on model #65420