Crash on saving or opening files with the Full Screen file browser window preference #76926

New Issue

Daniel Salazar · 2020-05-21T00:11:55+02:00

Daniel Salazar commented

2020-05-21 00:11:55 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87

Blender Version
Broken: version: 2.90 (sub 2), branch: master, commit date: 2020-05-19 22:32, hash: 4f622c9a08

Short description of error
The file browser crashes when the Full Screen
crash.txt

Exact steps for others to reproduce the error

Fresh factory settings
Go to preferences/Interface/Editors/Temporary Windows
Set the File Browser to Full Screen
Now save the blend file

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87 **Blender Version** Broken: version: 2.90 (sub 2), branch: master, commit date: 2020-05-19 22:32, hash: `4f622c9a08` **Short description of error** The file browser crashes when the Full Screen [crash.txt](https://archive.blender.org/developer/F8547731/crash.txt) **Exact steps for others to reproduce the error** - Fresh factory settings - Go to preferences/Interface/Editors/Temporary Windows - Set the File Browser to Full Screen ![image.png](https://archive.blender.org/developer/F8545569/image.png) - Now save the blend file

Daniel Salazar commented

2020-05-21 00:11:55 +02:00

Added subscriber: @zanqdo

blender-admin commented

2020-05-21 00:11:55 +02:00

#76972 was marked as duplicate of this issue

blender-admin commented

2020-05-21 00:11:55 +02:00

#76910 was marked as duplicate of this issue

Germano Cavalcante commented

2020-05-21 22:56:06 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-05-21 22:56:06 +02:00

I can't reproduce the crash.
Can you run blender_debug-gpu.cmd that is included in the download.
After Blender closes, the logs will be in a text file which can be attached here.

Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.50.01.05 26.20.15001.5006

I can't reproduce the crash. Can you run `blender_debug-gpu.cmd` that is included in the download. After Blender closes, the logs will be in a text file which can be attached here. ---- **Operating system:** Windows-10-10.0.18941 64 Bits **Graphics card:** Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.50.01.05 26.20.15001.5006

Daniel Salazar commented

2020-05-22 00:51:33 +02:00

Here they are

blender_system_info.txt

blender_debug_output.txt

Here they are [blender_system_info.txt](https://archive.blender.org/developer/F8546926/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8546927/blender_debug_output.txt)

Krystian Zajdel commented

2020-05-22 12:22:09 +02:00

Added subscriber: @enenra

Krystian Zajdel commented

2020-05-22 12:22:09 +02:00

I have the same issue. Saving the default cube crashes when file browser set to full screen.
What I find bizarre is that if I start blender with "./blender --debug-all" it doesn't crash.

System Information
Operating system: Linux-5.6.10-custom-x86_64-AMD_A8-5600K_APU_with_Radeon-tm-_HD_Graphics-with-slackware-14.2 64 Bits
Graphics card: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.36.0, 5.6.10-custom, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.2

Blender Version
Broken: version: 2.83 (sub 17), branch: master, commit date: 2020-05-21 08:18, hash: d15efbdc56
Worked: blender-2.83-008e96494008-linux64

I have the same issue. Saving the default cube crashes when file browser set to full screen. What I find bizarre is that if I start blender with "./blender --debug-all" it doesn't crash. **System Information** Operating system: Linux-5.6.10-custom-x86_64-AMD_A8-5600K_APU_with_Radeon-tm-_HD_Graphics-with-slackware-14.2 64 Bits Graphics card: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.36.0, 5.6.10-custom, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.2 **Blender Version** Broken: version: 2.83 (sub 17), branch: master, commit date: 2020-05-21 08:18, hash: `d15efbdc56` Worked: blender-2.83-008e96494008-linux64

Germano Cavalcante commented

2020-05-22 14:29:24 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Germano Cavalcante commented

2020-05-22 14:29:47 +02:00

Added subscriber: @ErickNyanduKabongo

Julian Eisel commented

2020-05-22 14:58:07 +02:00

Added subscriber: @JulianEisel

Julian Eisel self-assigned this 2020-05-22 14:58:07 +02:00

Julian Eisel commented

2020-05-22 14:58:07 +02:00

Probably caused by 796412dca0 (not a 2.83 bug then). Investigating.

Probably caused by 796412dca0 (not a 2.83 bug then). Investigating.

Julian Eisel commented

2020-05-22 15:19:26 +02:00

Added subscribers: @dr.sybren, @JacquesLucke

Julian Eisel commented

2020-05-22 15:24:37 +02:00

No, this is actually caused by b75ce05c3b, so it is a 2.83 regression.

No, this is actually caused by b75ce05c3b, so it is a 2.83 regression.

Julian Eisel commented

2020-05-22 16:05:46 +02:00

The crash happens because the cancelling of the file browser removes its screen (as in bScreen). Before b75ce05c3b, the file browser event wouldn't be handled any further then. After it, it would still be passed to other areas, while the screen pointer was dangling.
All this is very fragile code that has caused many bugs already. It's another example where we would need some kind of "sandboxed" execution for destructive handlers. See D7795.

@JacquesLucke I think going back to your earlier approach in D7720 is the best solution. It fixes this crash, and also still fixes #75292 & #73579. Would've prefered the more general solution, but the one specific to UI-handlers is still totally acceptable.

The crash happens because the cancelling of the file browser removes its screen (as in `bScreen`). Before b75ce05c3b, the file browser event wouldn't be handled any further then. After it, it would still be passed to other areas, while the screen pointer was dangling. All this is very fragile code that has caused many bugs already. It's another example where we would need some kind of "sandboxed" execution for destructive handlers. See [D7795](https://archive.blender.org/developer/D7795). @JacquesLucke I think going back to your earlier approach in [D7720](https://archive.blender.org/developer/D7720) is the best solution. It fixes this crash, and also still fixes #75292 & #73579. Would've prefered the more general solution, but the one specific to UI-handlers is still totally acceptable.

blender-admin commented

2020-05-25 18:33:12 +02:00

This issue was referenced by 2dd6d0ce4b

This issue was referenced by 2dd6d0ce4b6d0b72274234073306982c3122c904

blender-admin commented

2020-05-25 18:33:12 +02:00

This issue was referenced by 6fbeded285

This issue was referenced by 6fbeded285466327831b901c652e13e742c44689

Julian Eisel commented

2020-05-25 18:37:45 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Julian Eisel closed this issue

2020-05-25 18:37:45 +02:00

Thomas Dinges added this to the 2.83 LTS milestone 2023-02-08 16:35:43 +01: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 on saving or opening files with the Full Screen file browser window preference #76926