Crash after pressing ctrl+s in file view #69495

New Issue

Marcin Twarowski · 2019-09-04T15:33:40+02:00

Marcin Twarowski commented

2019-09-04 15:33:40 +02:00

System Information
Operating system: Windows-10-10.0.16299 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15

Blender Version
Broken: version: 2.81 (sub 5), branch: master, commit date: 2019-09-04 00:01, hash: da25aca267

Exact steps for others to reproduce the error
It happens with new files that are not saved yet.

Create new scene.
Open file view ("File > Open")
Press ctrl+s
You can see that the button has changed from open to "Save Blender File":
Now all it takes is to press that button or to press "Cancel" to crash Blender.

Similarly, Blender crashes in "save" window.

Create new scene.
Open save menu ("File > Save")
Press ctrl+s
Now all it takes to crash Blender is to press any of the two buttons.

**System Information** Operating system: Windows-10-10.0.16299 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15 **Blender Version** Broken: version: 2.81 (sub 5), branch: master, commit date: 2019-09-04 00:01, hash: `da25aca267` **Exact steps for others to reproduce the error** It happens with new files that are not saved yet. - Create new scene. - Open file view ("File > Open") - Press ctrl+s - You can see that the button has changed from open to "Save Blender File": ![obraz.png](https://archive.blender.org/developer/F7716344/obraz.png) - Now all it takes is to press that button or to press "Cancel" to crash Blender. Similarly, Blender crashes in "save" window. - Create new scene. - Open save menu ("File > Save") - Press ctrl+s - Now all it takes to crash Blender is to press any of the two buttons.

Marcin Twarowski commented

2019-09-04 15:33:40 +02:00

Added subscriber: @MarcinTwarowski

tom k commented

2019-09-04 16:41:40 +02:00

Added subscriber: @tomjk

tom k commented

2019-09-04 16:41:40 +02:00

You can also ctrl+o, ctrl+s, ctrl+o to cause this (or ctrl+s, ctrl+o, ctrl+s).

If I run from desktop, the file browser window closes, blender hangs and maxes out a cpu core until killed.

If I run from terminal with --debug-all it will crash immediately with

Memoryblock wmEvent: double free
Aborted

You can also `ctrl+o, ctrl+s, ctrl+o` to cause this (or `ctrl+s, ctrl+o, ctrl+s`). If I run from desktop, the file browser window closes, blender hangs and maxes out a cpu core until killed. If I run from terminal with `--debug-all` it will crash immediately with ``` Memoryblock wmEvent: double free Aborted ```

Robert Guetzkow commented

2019-09-04 16:45:30 +02:00

Added subscriber: @rjg

Robert Guetzkow commented

2019-09-04 16:45:30 +02:00

Stack trace from ee8f69c96c

BKE_workspace_active_get(WorkSpaceInstanceHook * hook) Line 393	C
CTX_wm_window_set(bContext * C, wmWindow * win) Line 918	C
wm_handler_fileselect_do(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, int val) Line 2390	C
wm_handler_fileselect_call(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, const wmEvent * event) Line 2513	C
wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2900	C
wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 2952	C
wm_event_do_handlers(bContext * C) Line 3330	C
WM_main(bContext * C) Line 420	C
main(int argc, const unsigned char * * UNUSED_argv_c) Line 493	C

Stack trace from ee8f69c96cba ``` BKE_workspace_active_get(WorkSpaceInstanceHook * hook) Line 393 C CTX_wm_window_set(bContext * C, wmWindow * win) Line 918 C wm_handler_fileselect_do(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, int val) Line 2390 C wm_handler_fileselect_call(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, const wmEvent * event) Line 2513 C wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2900 C wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 2952 C wm_event_do_handlers(bContext * C) Line 3330 C WM_main(bContext * C) Line 420 C main(int argc, const unsigned char * * UNUSED_argv_c) Line 493 C ```

Julian Eisel commented

2019-09-05 12:53:25 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2019-09-05 12:53:25 +02:00

For the records, I'm investigating this, but it's a tricky one.
Basically the file browser handler is destroying the window currently set active by the event handling, which is left with dangling pointers then. One solution would be doing a delayed destruction of the window (like we sometimes delay closing of Blender, i.e. wm_exit_schedule_delayed()). However I'm trying to understand why this usually isn't an issue, but it's difficult to debug.

For the records, I'm investigating this, but it's a tricky one. Basically the file browser handler is destroying the window currently set active by the event handling, which is left with dangling pointers then. One solution would be doing a delayed destruction of the window (like we sometimes delay closing of Blender, i.e. `wm_exit_schedule_delayed()`). However I'm trying to understand why this usually isn't an issue, but it's difficult to debug.

Julian Eisel self-assigned this 2019-09-05 12:53:33 +02:00

blender-admin commented

2019-09-05 23:34:09 +02:00

This issue was referenced by fbf6898f58

This issue was referenced by fbf6898f583fe9982ca13366166a5505a94789ed

Julian Eisel commented

2019-09-05 23:59:10 +02:00

Changed status from 'Open' to: 'Resolved'

Julian Eisel closed this issue

2019-09-05 23:59:10 +02:00

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

Crash after pressing ctrl+s in file view #69495