Crash while attempting to use the file save dialog window #117923

New Issue

Daniel-Guenther · 2024-02-06T22:44:52+01:00

Daniel-Guenther commented

2024-02-06 22:44:52 +01:00

System Information

Operating System: Windows 10
Blender Versions: 3.3, 3,6, 4.0
Hardware Specifications: i5-10400F, NVIDIA RTX 4070, 128 GB RAM

Short description of error
I'm using Blender on Windows 10, and regularly when I try to use the Blender file dialog window
blender will not open it, but entirely crash. It doesn't happen every time, but after a few
hours of work it will start crashing every time a file dialog window is open, and once such a crash
has occurred Blender will thereafter crash every time I try to restart the program
until I restart my machine (or re-sign in to windows).

Actions that can cause this crash include any file dialog actions, such as:

save as
open file
save image or render to file
specify output path (file dialog button)
append
link

However note that these actions can still be done in Blender
via python scripts, it just cannot be done via the GUI because
the file dialog window causes Blender to crash.

Once such a crash occurred, Blender fails to open again, it will show a
window for an instant then disappear within about 100ms, and when starting blender.exe
via the command line I receive the message "segmentation fault".

If I happen to have another instance
of Blender running in the background, it will instantly crash as
soon as I use any of the file dialog window functions mentioned earlier.

Based on some debugging below I found that the issue appears to be related to wintab.
I do not use tablets and don't have one plugged in, but I believe other people have used
tablets on this computer before me.

Exact steps for others to reproduce the error
(sometimes):

open the default blender startup
File -> save as

Some initial debugging
I recompiled blender using "./make.bat debug" using the git repository
using branch "blender-v4.0-release" (git commit 88559c00cd),
and was able to get the following text starting up Blender 4.0 using gdb:

Thread 1 received signal SIGSEGV, Segmentation fault.
0x00007ffcf3481346 in Wintab32!WTOpenW () from C:\Windows\SYSTEM32\wintab32.dll

(and I've included gdb-log1.txt with some more information).

I've started up the process using windbg, and have attached a number of files which
reveal the debug log, where "WinDbg*1.txt" are for an instance of the debug-compiled
blender which crashed immediately after startup, and "WinDbg*2.txt" are for an instance
of blender which started up correctly, but crashed after attempting to use the "save as"
dialog window.

Notably take a look at the WinDbg-log2.txt call stack (below line 173) which indicates there's a Crash
occurring in "D:\daniel-work\blender-git\blender\intern\ghost\intern\GHOST_Wintab.cc @ 85", but I don't know enough to understand it.

## System Information - Operating System: Windows 10 - Blender Versions: 3.3, 3,6, 4.0 - Hardware Specifications: i5-10400F, NVIDIA RTX 4070, 128 GB RAM **Short description of error** I'm using Blender on Windows 10, and regularly when I try to use the Blender file dialog window blender will not open it, but entirely crash. It doesn't happen every time, but after a few hours of work it will start crashing every time a file dialog window is open, and once such a crash has occurred Blender will thereafter crash every time I try to restart the program until I restart my machine (or re-sign in to windows). Actions that can cause this crash include any file dialog actions, such as: - save as - open file - save image or render to file - specify output path (file dialog button) - append - link However note that these actions can still be done in Blender via python scripts, it just cannot be done via the GUI because the file dialog window causes Blender to crash. Once such a crash occurred, Blender fails to open again, it will show a window for an instant then disappear within about 100ms, and when starting blender.exe via the command line I receive the message "segmentation fault". If I happen to have another instance of Blender running in the background, it will instantly crash as soon as I use any of the file dialog window functions mentioned earlier. Based on some debugging below I found that the issue appears to be related to wintab. I do not use tablets and don't have one plugged in, but I believe other people have used tablets on this computer before me. **Exact steps for others to reproduce the error** (sometimes): - open the default blender startup - File -> save as **Some initial debugging** I recompiled blender using "./make.bat debug" using the git repository using branch "blender-v4.0-release" (git commit 88559c00cd36bb706ae928021777e269570107a8), and was able to get the following text starting up Blender 4.0 using gdb: ``` Thread 1 received signal SIGSEGV, Segmentation fault. 0x00007ffcf3481346 in Wintab32!WTOpenW () from C:\Windows\SYSTEM32\wintab32.dll ``` (and I've included gdb-log1.txt with some more information). I've started up the process using windbg, and have attached a number of files which reveal the debug log, where "WinDbg\*1.txt" are for an instance of the debug-compiled blender which crashed immediately after startup, and "WinDbg\*2.txt" are for an instance of blender which started up correctly, but crashed after attempting to use the "save as" dialog window. Notably take a look at the WinDbg-log2.txt call stack (below line 173) which indicates there's a Crash occurring in "D:\daniel-work\blender-git\blender\intern\ghost\intern\GHOST_Wintab.cc @ 85", but I don't know enough to understand it.

gdb-log1.txt

4.5 KiB

WinDbg-log2.txt

23 KiB

WinDbg-env1.txt

31 KiB

WinDbg-analyze1.txt

5.5 KiB

WinDbg-commands.txt

130 B

WinDbg-log1.txt

4.4 KiB

WinDbg-stack1.txt

4.1 KiB

Daniel-Guenther added the

labels 2024-02-06 22:44:53 +01:00

Iliya Katushenock added the

Platform

Windows

label 2024-02-06 22:47:58 +01:00

Daniel-Guenther commented

2024-02-06 23:07:35 +01:00

I found issue #116095 which seems to have similar symptoms

Iliya Katushenock commented

2024-02-07 01:19:22 +01:00

If I happen to have another instance
of Blender running in the background, it will instantly crash as
soon as I use any of the file dialog window functions mentioned earlier.

This looks like: #115940.

Can you check if your drivers is updated?

> If I happen to have another instance of Blender running in the background, it will instantly crash as soon as I use any of the file dialog window functions mentioned earlier. This looks like: #115940. Can you check if your drivers is updated?

Pratik Borhade commented

2024-02-07 07:22:07 +01:00

Hi, thanks for the report and investigation. This is same as #111152, closing

Pratik Borhade closed this issue

2024-02-07 07:22:10 +01:00

Blender Bot added

and removed

labels 2024-02-07 07:22:11 +01:00

Pratik Borhade commented

2024-02-07 07:24:27 +01:00

Can you check if your drivers is updated?

Since @Daniel-Guenther is not using tablet, I'd suggest to remove wintab32.dll from the device.
Crash due to wintab32.dll has been observed/reported many times when dealing with floating windows.

> Can you check if your drivers is updated? Since @Daniel-Guenther is not using tablet, I'd suggest to remove wintab32.dll from the device. Crash due to `wintab32.dll` has been observed/reported many times when dealing with floating windows.

Daniel-Guenther commented

2024-02-28 19:45:37 +01:00

I switched the Tablet API to "Windows Ink", and I can confirm I have not seen this crash again in the last 3 weeks. Since I don't use a tablet this change doesn't otherwise impact my work.

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 while attempting to use the file save dialog window #117923

System Information