[Bug 49082] New: God Eater 3 has 100% CPU usage a few minutes after entering lobby, infinite loading screen

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49082

Bug ID: 49082
           Summary: God Eater 3 has 100% CPU usage a few minutes after
                    entering lobby, infinite loading screen
           Product: Wine
           Version: 5.7
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

When running God Eater 3, the game will load properly at first, character
creation is possible. Once you're placed in the lobby however, CPU usage will
suddenly increase to 100% a few minutes in (regardless of what you do), and
it's impossible to load the next mission, as the loading screen hangs forever
(CPU usage remains at 100%).

[Bug 49082] God Eater 3 has 100% CPU usage a few minutes after entering lobby, infinite loading screen

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49082

Olivier F. R. Dierick  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Olivier F. R. Dierick  ---
Hello,

Please attach a normal (=without WINEDEBUG) terminal output.
Instructions to get a log can be found there:
https://wiki.winehq.org/FAQ#get_log

Regards.

[Bug 49082] God Eater 3 has 100% CPU usage a few minutes after entering lobby, infinite loading screen

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49082

--- Comment #2 from qsniyg  ---
(In reply to Olivier F. R. Dierick from comment #1)
> Hello,
>
> Please attach a normal (=without WINEDEBUG) terminal output.
> Instructions to get a log can be found there:
> https://wiki.winehq.org/FAQ#get_log
>
> Regards.

I don't have the game currently installed (I just reported this bug because I
noticed I hadn't earlier), but there are many logs available in the proton
github issues page: https://github.com/ValveSoftware/Proton/issues/2418

Although the logs are from proton, I tested it using wine and the same issue
occurs.