Crash when using pen pressure

I think it's a bug...
#1

When using the ‘Brush scale’ checkbox in the Pen tab. After drawing for a minute it reliably crashes every time.

I cant attach the bug report here but I can email.

date/time : 2023-10-20, 15:26:03, 126ms
computer name : NOODLES
user name : jason
operating system : Windows 10 x64 build 22621
system language : English
system up time : 1 day 4 hours
program up time : 1 minute 8 seconds
processors : 32x 13th Gen Intel(R) Core™ i9-13900HX
physical memory : 15385/32508 MB (free/total)
free disk space : (C:) 765.55 GB
display mode : 2560x1440, 32 bit
process id : $4848
allocated memory : 165.23 MB
largest free block : 128847.06 GB
executable : pmotion.exe
exec. date/time : 2023-10-01 18:27
version : 8.0.5.0
compiled with : Delphi 11
madExcept version : 5.1.2
contact name : Jason
callstack crc : $4de7fcf5, $7d9534a9, $7d9534a9
exception number : 1
exception class : EInvalidOp
exception message : Invalid floating point operation.

main thread ($7940):
7ffb5171 +06c KERNELBASE.dll RaiseException
7ffb51c0 +08f ucrtbase.dll sqrt
7ffb2162 +1ab Ninput.dll DefaultInputHandler
7ffb51ed +086 USER32.dll CallWindowProcW
0104c7ac +10c pmotion.exe Vcl.Controls 10624 +30 TWinControl.DefaultHandler
00d90300 +050 pmotion.exe System 18825 +13 TObject.Dispatch
010451cd +36d pmotion.exe Vcl.Controls 7548 +91 TControl.WndProc
0104c63b +97b pmotion.exe Vcl.Controls 10583 +170 TWinControl.WndProc
0104b7da +02a pmotion.exe Vcl.Controls 10271 +3 TWinControl.MainWndProc
00f6d163 +023 pmotion.exe System.Classes 18392 +8 StdWndProc
7ffb51ed +1fc USER32.dll DispatchMessageW
0119154e +12e pmotion.exe Vcl.Forms 11336 +23 TApplication.ProcessMessage
011915c3 +013 pmotion.exe Vcl.Forms 11366 +1 TApplication.HandleMessage
01191a1a +0ea pmotion.exe Vcl.Forms 11505 +27 TApplication.Run
01a30ec3 +1e3 pmotion.exe Pmotion 1151 +61 initialization
7ffb53d0 +018 KERNEL32.DLL BaseThreadInitThunk
7ffb541a +022 ntdll.dll RtlUserThreadStart

thread $9e38:
7ffb53d0 +18 KERNEL32.DLL BaseThreadInitThunk
7ffb541a +22 ntdll.dll RtlUserThreadStart

thread $4d20:
7ffb53d0 +18 KERNEL32.DLL BaseThreadInitThunk
7ffb541a +22 ntdll.dll RtlUserThreadStart

thread $90f8:
7ffb53d0 +18 KERNEL32.DLL BaseThreadInitThunk
7ffb541a +22 ntdll.dll RtlUserThreadStart

thread $60b4:
7ffb516e +87 KERNELBASE.dll WaitForSingleObjectEx
7ffb53d0 +18 KERNEL32.DLL BaseThreadInitThunk
7ffb541a +22 ntdll.dll RtlUserThreadStart

thread $78d4:
7ffb516d +4c KERNELBASE.dll GetQueuedCompletionStatus
7ffb53d0 +18 KERNEL32.DLL BaseThreadInitThunk
7ffb541a +22 ntdll.dll RtlUserThreadStart

thread $39ec:
7ffb541b +136 ntdll.dll RtlSleepConditionVariableSRW
7ffb5172 +022 KERNELBASE.dll SleepConditionVariableSRW
7ffb53d0 +018 KERNEL32.DLL BaseThreadInitThunk
7ffb541a +022 ntdll.dll RtlUserThreadStart

#2

Thanks for the report. It looks as if the crash appears outside of the actual program executable. I can’t even see any of “my code” in the stack trace. The code that I can see is part of the dev system I use and Windows modules.
But still the problem can occur because “my code” did something wrong before the actual error occurs.

Is this a new problem that did not happen before 8.0.5?
Does it only happen with brush scale option and not with others?
May I send you special debug build? If so then please write to jan@cosmigo.com and refer to this post. Otherwise I don’t have a starting point for further analysis.

#3

Thanks Jan, the error is a combination of the Xencelabs tablet and Pro motion. When I switch to using the Wacom hardware / drivers it works great.

#4

I’m getting the exact same thing, how did you fix it? I remember adding promotion to xencelabs driver program today and since then it’s been crashing non stop. I will remove it again and see how that goes

1 Like
#5

Crash was happening every few minutes with WINAPI and XENCELABS tablet.

However I couldn’t get it to pick up the pen pressure at all with WINTAB. However, after some back and forth I’ve managed to get it to work with the WinTab option now by re-adding it to the Xencelab driver program as a custom app, then turning OFF windows ink there and restarting pro-motion, now it’s picked up the pen pressure.

The next test will now be to see if it crashes like it did with WinApi. I will post back and let you know how I get on…

1 Like
#6

Just a quick check in as promised. After setting it up as above I’ve not had any crashes with the pen and everything is working great!

3 Likes