I can reproduce this locally and debian10 has no issues on a manual run:
https://testbot.winehq.org/JobDetails.pl?Key=56235

Op wo 4 sep. 2019 om 16:11 schreef Marvin <testbot@winehq.org>:
Hi,

While running your changed tests, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?

Full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=56228

Your paranoid android.


=== debian10 (32 bit report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00439c82).

Report errors:
kernel32:virtual prints too much data (91050 bytes)

=== debian10 (32 bit Chinese:China report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00439c82).

Report errors:
kernel32:virtual prints too much data (91050 bytes)

=== debian10 (build log) ===

Task errors:
DBI connect('winetestbot','winetestbot',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /home/testbot/lib/ObjectModel/DBIBackEnd.pm line 54.

DBI connect('winetestbot','winetestbot',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /home/testbot/lib/ObjectModel/DBIBackEnd.pm line 54.


=== debian10 (32 bit WoW report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00439c82).

Report errors:
kernel32:virtual prints too much data (91050 bytes)

=== debian10 (64 bit WoW report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00439c82).

Report errors:
kernel32:virtual prints too much data (91050 bytes)