Wintab crash on window close. #85799

New Issue

Ernesto Méndez · 2021-02-19T19:55:56+01:00

Ernesto Méndez commented

2021-02-19 19:55:56 +01:00

System Information
Operating system: Windows 10
Graphics card: Nvidia Quadro P5000

Blender Version
Broken: 2.91.2
Worked: N/A

OBJ Importer crashes while attempting to import OBJ file.

Steps to reproduce:

Download attached OBJ
File > Import > Wavefront (obj)
Select OBJ, click "Import OBJ"

Actual Behavior:
Blender crashes.

Expected Behavior:
The OBJ file is imported successfully.

testPM3D_Sphere3D1.zip

**System Information** Operating system: Windows 10 Graphics card: Nvidia Quadro P5000 **Blender Version** Broken: 2.91.2 Worked: N/A OBJ Importer crashes while attempting to import OBJ file. **Steps to reproduce:** 1. Download attached OBJ 2. File > Import > Wavefront (obj) 3. Select OBJ, click "Import OBJ" **Actual Behavior:** Blender crashes. **Expected Behavior:** The OBJ file is imported successfully. --- [testPM3D_Sphere3D1.zip](https://archive.blender.org/developer/F9818660/testPM3D_Sphere3D1.zip)

Ernesto Méndez commented

2021-02-19 19:55:56 +01:00

Added subscriber: @mendezcode

blender-admin commented

2021-02-19 19:55:56 +01:00

#86039 was marked as duplicate of this issue

Stephen Swaney commented

2021-02-20 20:01:12 +01:00

Added subscriber: @StephenSwaney

Stephen Swaney commented

2021-02-20 20:01:12 +01:00

Imports fine here. Linux 2.92.0 RC and 2.91.2
I suspect a local problem.
Any interesting error messages?

Imports fine here. Linux 2.92.0 RC and 2.91.2 I suspect a local problem. Any interesting error messages?

Ernesto Méndez commented

2021-02-21 02:52:52 +01:00

Seems like it's something with my system... You know what... I should've provided you with more debugging info, my bad.

Here's what I get when I run it from the console:

Read prefs: C:\Users\me\AppData\Roaming\Blender Foundation\Blender\2.91\config\userpref.blend
found bundled python: C:\Programs\blender\2.91\python
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF8E52427DA
Module  : Wintab32.dll
Thread  : 000056c4
Writing: C:\Users\me\AppData\Local\Temp\blender.crash.txt```

I think this may be an isolated issue on my system if it imports fine for you. I haven't updated Windows in a while to keep it running stable, so this may be the cause.

In any case, I have attached the crash report.

[blender.crash.txt.zip](https://archive.blender.org/developer/F9823628/blender.crash.txt.zip)

Thanks!

Seems like it's something with my system... You know what... I should've provided you with more debugging info, my bad. Here's what I get when I run it from the console: ```PS C:\Programs\blender> .\blender.exe Read prefs: C:\Users\me\AppData\Roaming\Blender Foundation\Blender\2.91\config\userpref.blend found bundled python: C:\Programs\blender\2.91\python Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF8E52427DA Module : Wintab32.dll Thread : 000056c4 Writing: C:\Users\me\AppData\Local\Temp\blender.crash.txt``` I think this may be an isolated issue on my system if it imports fine for you. I haven't updated Windows in a while to keep it running stable, so this may be the cause. In any case, I have attached the crash report. [blender.crash.txt.zip](https://archive.blender.org/developer/F9823628/blender.crash.txt.zip) Thanks!

Ernesto Méndez commented

2021-02-21 03:09:45 +01:00

Update: I have installed the latest GPU drivers, but it seems this is related to the tablet drivers (based on searches for wintab32.dll)... I do use a tablet screen, so I think this may have something to do with Wacom's drivers or something...

Ernesto Méndez commented

2021-02-21 03:18:15 +01:00

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

Ernesto Méndez closed this issue

2021-02-21 03:18:15 +01:00

Ernesto Méndez self-assigned this 2021-02-21 03:18:15 +01:00

Ernesto Méndez commented

2021-02-21 03:18:15 +01:00

Sooo.... I was able to fix it! This actually is not a localized problem but it does seem like a bug.

I was able to import fine after setting the Tablet API to "Windows Ink" on Preferences > Input.

That being said, this doesn't seem to be a bug with the OBJ importer per se, but this highlights another possible bug which involves Blender crashing when using "WinTab" as tablet API for some reason.

In any case, I'm glad it's solved, thanks again!

Sooo.... I was able to fix it! This actually is not a localized problem but it does seem like a bug. I was able to import fine after setting the Tablet API to "Windows Ink" on Preferences > Input. ![2021-02-20 22-14-30.png](https://archive.blender.org/developer/F9823692/2021-02-20_22-14-30.png) That being said, this doesn't seem to be a bug with the OBJ importer per se, but this highlights another possible bug which involves Blender crashing when using "WinTab" as tablet API for some reason. In any case, I'm glad it's solved, thanks again!

👍 1

Ankit Meel commented

2021-02-21 06:14:09 +01:00

Added subscribers: @PrototypeNM1, @ankitm

Ankit Meel commented

2021-02-21 06:14:09 +01:00

CC @PrototypeNM1

Nicholas Rishel commented

2021-02-21 07:37:23 +01:00

Changed status from 'Resolved' to: 'Confirmed'

Nicholas Rishel reopened this issue

2021-02-21 07:37:23 +01:00

Nicholas Rishel commented

2021-02-21 07:37:23 +01:00

What's happening here is that while the window is being destroyed, it closes the Wintab context via WTClose. The Wintab library must be calling one of the Win32 functions which allows callbacks to the Windows event loop to run, which calls an event which uses Wintab after it's closed and while Ghost's window is half torn down.

~~The solution here is to not trust Wintab when tearing down the window to not reenter, and close before the GHOST_WindowWin32's destructor. Reopening as this is a legitimate issue.~~

Edit: The issue is reentrancy while GHOST_WindowWin32 is being torn down, but it's not Wintab that triggers it, Wintab being passed a closed context is just the last step. Looks like it's the call to DestroyWindow from the stack trace.

Edit2: Without logging with the specific device, it could be quite difficult to narrow down the exact cause. E.g. it could be that the Wintab library is not handling multiple contexts for a single process correctly and thus closing the wrong one, or reentrancy is causing a half-destroyed window with closed Wintab context to crash.

~~What's happening here is that while the window is being destroyed, it closes the Wintab context via WTClose. The Wintab library must be calling one of the Win32 functions which [allows callbacks to the Windows event loop to run](https://docs.microsoft.com/en-us/windows/win32/winauto/guarding-against-reentrancy-in-hook-functions), which calls an event which uses Wintab after it's closed and while Ghost's window is half torn down.~~ ~~The solution here is to not trust Wintab when tearing down the window to not reenter, and close before the GHOST_WindowWin32's destructor. Reopening as this is a legitimate issue.~~ Edit: The issue is reentrancy while GHOST_WindowWin32 is being torn down, but it's not Wintab that triggers it, Wintab being passed a closed context is just the last step. Looks like it's the call to DestroyWindow from the stack trace. Edit2: Without logging with the specific device, it could be quite difficult to narrow down the exact cause. E.g. it could be that the Wintab library is not handling multiple contexts for a single process correctly and thus closing the wrong one, or reentrancy is causing a half-destroyed window with closed Wintab context to crash.

Ernesto Méndez was unassigned by Ankit Meel

2021-02-21 07:38:43 +01:00

Nicholas Rishel self-assigned this 2021-02-21 08:06:56 +01:00

Nicholas Rishel commented

2021-03-02 19:25:02 +01:00

Added subscribers: @kamiyu1031, @rjg

Nicholas Rishel changed title from ~~OBJ Importer Crash~~ to Wintab crash on window close.

2021-03-02 19:26:04 +01:00

Nicholas Rishel commented

2021-03-02 22:09:22 +01:00

@mendezcode @kamiyu1031 Could you recreate the crash in this build, copy the content of blender_debug_output.txt to this link, and link the result here?

@mendezcode @kamiyu1031 Could you recreate the crash in [this build](https:*builder.blender.org/download/T85799/T85799-blender-2.93.0-577577bd6d3a-windows64.zip), copy the content of blender_debug_output.txt to [this link](https:*developer.blender.org/paste/edit/form/default/), and link the result here?

Nicholas Rishel commented

2021-03-02 22:09:49 +01:00

Changed status from 'Confirmed' to: 'Needs User Info'

Ernesto Méndez commented

2021-03-03 15:49:42 +01:00

@PrototypeNM1 Tested and crash persists, here's the paste: https://developer.blender.org/P2009

Philipp Oeser commented

2021-03-24 15:27:08 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Ankit Meel commented

2021-06-10 14:17:51 +02:00

Could you upload C:\Users\mdz\AppData\Local\Temp\blender.crash.txt ?

Could you upload `C:\Users\mdz\AppData\Local\Temp\blender.crash.txt` ?

Nicholas Rishel commented

2021-06-22 22:16:21 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Nicholas Rishel commented

2021-06-22 22:16:21 +02:00

@mendezcode Could you confirm is the issue is still present in current daily builds ? There were a lot of recent changes with how Wintab opened and closed in Blender which should resolve any issues.

@mendezcode Could you confirm is the issue is still present in [current daily builds ](https://builder.blender.org/download/daily/blender-3.0.0-alpha+master.e3bdb189a777-windows.amd64-release.zip)? There were a lot of recent changes with how Wintab opened and closed in Blender which should resolve any issues.

Ernesto Méndez commented

2021-06-23 13:45:37 +02:00

@PrototypeNM1 tested and the issue is no longer present, it has been fixed.

Ankit Meel commented

2021-06-23 13:51:32 +02:00

Changed status from 'Needs User Info' to: 'Resolved'

Ankit Meel closed this issue

2021-06-23 13:51:32 +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

Wintab crash on window close. #85799