https://bugs.winehq.org/show_bug.cgi?id=57960
Bug ID: 57960 Summary: ChessBase 18 hangs / stops accepting input a few seconds after launch Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: winehq@brobston.com Regression SHA1: fd539487b7860ff0a53474aa6fbcbe229f3f42c1 Distribution: Ubuntu
Created attachment 78212 --> https://bugs.winehq.org/attachment.cgi?id=78212 Log from first bad commit with most warnings enabled
I'm running with "Emulate a virtual desktop" active. I can start ChessBase 18 from the command line with `WINEDEBUG="-warn+all,warn-dpa" wine start "C:\Program Files\ChessBase\CBase18\CBase18.exe"` in a 64-bit prefix. The application launches as usual, but after a few seconds, it stops responding to the mouse altogether. The CBase18.exe process consumes around 200% CPU as shown in `top` when this situation occurs. The log output does show new log entries when I focus or unfocus the virtual-desktop window, but otherwise, it does not typically appear to be logging anything. I then stop the process from the command line with, for instance, `killall CBase18.exe`.
I will attach a log from the first bad commit and, shortly thereafter, the last good commit.
https://bugs.winehq.org/show_bug.cgi?id=57960
--- Comment #1 from winehq@brobston.com --- Created attachment 78213 --> https://bugs.winehq.org/attachment.cgi?id=78213 Logs from last good commit with most warnings enabled
https://bugs.winehq.org/show_bug.cgi?id=57960
winehq@brobston.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=57960
winehq@brobston.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |julliard@winehq.org
https://bugs.winehq.org/show_bug.cgi?id=57960
--- Comment #2 from winehq@brobston.com --- I neglected to cc the commit author when I created this bug report -- apologies!