[Bug 49590] New: Battle.net Agent.exe hang/crash

[WineHQ Bugzilla]

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

            Bug ID: 49590
           Summary: Battle.net Agent.exe hang/crash
           Product: Wine-staging
           Version: 5.13
          Hardware: x86-64
               URL: https://www.blizzard.com/apps/battle.net/desktop
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: maciej.stanczew+b at gmail.com
                CC: leslie_alistair at hotmail.com, z.figura12 at gmail.com
      Distribution: ArchLinux

On Staging 5.13, when using Battle.net App, its Agent.exe process will often
(not always) misbehave. Example behavior:
- Crashes on launch -- can be verified by processes dying and new ones being
spawned, and by empty "Crash.txt" file in
'drive_c/ProgramData/Battle.net/Agent/Agent.<version>/Errors';
- Hangs using 100% CPU and doesn't exit when Battle.net App is closed;
- Blocks launching of games; for example when launching Diablo III, I see
'Diablo' in process list, but it won't actually launch the game until I kill
Agent.exe (which at the time is hanged with 100% CPU consumption).

Sometimes error message BLZBNTBNA00000005 will be shown in Battle.net App,
which is described as:
"The Blizzard Battle.net desktop app failed to communicate with the Blizzard
Update Agent, which is required to install, update, launch, and uninstall
Blizzard games."
https://battle.net/support/en/article/16531

This is not happening with both Staging 5.12 and with vanilla Wine 5.13. With
those versions, a single Agent.exe lives alongside Battle.net App, doesn't
hang, and exits when Battle.net App is closed. I'm not able to check
cooperation with games on those versions because of bug 45349 and bug 42741.

Since Agent.exe is spawned by Battle.net App, it's difficult to get Wine logs
for its execution. If I launch Agent.exe manually (without Battle.net App), it
seems to not hang/crash.

I only managed to get two exceptions when Battle.net App was running; one when
I manually launched Agent.exe when previous instance died:
07c0:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr
0x7bc265b8

and I'm not even sure how I got the second one, as it happened only once and
I've been unable to reproduce it again -- but hey, it might be useful:
01f8:err:virtual:virtual_setup_exception stack overflow 976 bytes in thread
01f8 addr 0xf7a91c2e stack 0x220c30 (0x220000-0x221000-0x320000)

I'll try to do a bisection next, to find where in Staging 5.13 the problem was
introduced/uncovered.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.