Dragging incorrect object into reference field - Crashes Blender #62760

New Issue

Eric · 2019-03-20T03:16:23+01:00

Eric commented

2019-03-20 03:16:23 +01:00

System Information
Operating system: Windows 7
Graphics card: GT750M

Blender Version
Broken: 2.80, March 19, 22:51:20 - 2eead48688
Worked: This has been happening in all 2.8 beta releases I've tried.

Short description of error
Dragging an incorrect object (such as a cube) to a field that asks for an object reference (ex. "Taper Object"), then directly clicking in that field causes Blender to shutdown.

Exact steps for others to reproduce the error

Create a Text object and Cube.
Select the text then go to the "Object Data"/"a" tab.
Under "Geometry", drag the Cube layer into the "Taper Object" field
Nothing will happen clearly, BUT without moving the mouse out of the field, click it. (If you move the cursor out of the field first, then click, it does not crash.)
5 Blender will crash and close.
** This happens with most "reference" fields I believe.

Note: An expert blender user wouldn't attempt this, but I am a new user and tend to try weird things in order to learn. I apologize.

**System Information** Operating system: Windows 7 Graphics card: GT750M **Blender Version** Broken: 2.80, March 19, 22:51:20 - 2eead4868834 Worked: This has been happening in all 2.8 beta releases I've tried. **Short description of error** Dragging an incorrect object (such as a cube) to a field that asks for an object reference (ex. "Taper Object"), then directly clicking in that field causes Blender to shutdown. **Exact steps for others to reproduce the error** 1. Create a Text object and Cube. 2. Select the text then go to the "Object Data"/"a" tab. 3. Under "Geometry", drag the Cube layer into the "Taper Object" field 4. Nothing will happen clearly, BUT without moving the mouse out of the field, click it. (If you move the cursor out of the field first, then click, it does not crash.) 5 Blender will crash and close. ** This happens with most "reference" fields I believe. Note: An expert blender user wouldn't attempt this, but I am a new user and tend to try weird things in order to learn. I apologize.

Eric commented

2019-03-20 03:16:23 +01:00

Added subscriber: @Air_Bear

Bastien Montagne self-assigned this 2019-03-20 10:44:30 +01:00

Bastien Montagne removed their assignment 2019-03-20 12:17:32 +01:00

Campbell Barton was assigned by Bastien Montagne

2019-03-20 12:17:32 +01:00

Bastien Montagne commented

2019-03-20 12:17:32 +01:00

Added subscribers: @ideasman42, @mont29

Bastien Montagne commented

2019-03-20 12:17:32 +01:00

Transferring that to @ideasman42, spent over an hour trying to understand what happens here and still have no clue… Maybe you can do better?

Origin of the crash is obvious (search_func of the button is called with a NULL search_func_arg in ui_searchbox_update(), but I cannot see what leads to that situation.

Only difference I noticed so far when dragging invalid data vs. valid data is that after a valid data drag, we have two calls in a row to UI_but_func_search_set(), while when dragged data is invalid, we only have one.

Quickslap test file to reproduce: drag_drop_invalid_ID_in_search_field.blend

Transferring that to @ideasman42, spent over an hour trying to understand what happens here and still have no clue… Maybe you can do better? Origin of the crash is obvious (`search_func` of the button is called with a NULL `search_func_arg` in `ui_searchbox_update()`, but I cannot see what leads to that situation. Only difference I noticed so far when dragging invalid data vs. valid data is that after a valid data drag, we have two calls in a row to `UI_but_func_search_set()`, while when dragged data is invalid, we only have one. Quickslap test file to reproduce: [drag_drop_invalid_ID_in_search_field.blend](https://archive.blender.org/developer/F6854502/drag_drop_invalid_ID_in_search_field.blend)

Jacques Lucke commented

2019-03-20 14:26:05 +01:00

Added subscriber: @JacquesLucke