Open dacap opened 2 years ago
Sentry issue: ASEPRITE-2B
Sentry issue: ASEPRITE-P
The https://sentry.io/organizations/igara-studio/issues/2989300328/ is not related to Wintab, it's a bug from our side, fixed here. The Wacom team help us to identify the issue (we're too used to wintab32.dll bugs, but that one in particular is unrelated).
Probably all these crashes are related to just one specific wintab32.dll of one specific vendor.
{
Comments: Graphics Tablet Driver,
CompanyName: Graphics Tablet,
FileDescription: wintab32 Dynamic Link Library,
FileVersion: 9, 0, 0, 1,
InternalName: wintab32,
LegalCopyright: Copyright (C) 2014,
OriginalFilename: wintab32.dll,
ProductName: wintab32 Dynamic Link Library,
ProductVersion: 9, 0, 0, 1
}
Just updated the description as we already know that most of the crashes came from HUION drivers. We might disable them if we don't find other solution (asking the user to update the driver and contact HUION customer support)
A long-standing issue between Aseprite <-> wintab32.dll is all kind of crashes related to the interaction between our code and Wintab implementations. We are not sure if we are using 100% right the API, or if it's related to bugs in Wintab impls, so we aren't sure what to do in these cases.
There is a long history about this:
-disable-wintab
parameter, then Tablet options, changing to Windows pointer API by default, etc.) A lot of .dmp files received by users manually, and now from Sentry.Internal Sentry reports:
It looks like these reports are related to a HUION driver mainly. Although the .dll info is anonymous:
We've received from Sentry the debug info from the wintab32.dll and these are the paths where the .pdb should be located:
And doing a Google search it looks like the file came from HUION Drivers.
We tried to contact HUION Customer Support, but weren't contacted by their development team, in a near future we might completely disable this wintab32 asking users to report the problem to Huion directly (and forcing Windows API in these cases).