[Bug 49590] Battle.net Agent.exe hang/crash
WineHQ Bugzilla
wine-bugs at winehq.org
Mon Jul 20 16:44:19 CDT 2020
https://bugs.winehq.org/show_bug.cgi?id=49590
--- Comment #1 from Maciej Stanczew <maciej.stanczew+b at gmail.com> ---
Created attachment 67765
--> https://bugs.winehq.org/attachment.cgi?id=67765
Logs
Results are in:
f6954e6e77dfd443f5bdc28190ad478e0d6fb77d is the first bad commit
commit f6954e6e77dfd443f5bdc28190ad478e0d6fb77d
Author: Zebediah Figura <z.figura12 at gmail.com>
Date: Wed Jul 8 20:46:51 2020 -0500
Rebase against 262e4ab9e0eeb126dde5cb4cba13fbf7f1d1cef0.
For reproduction with logs, I have to kill the Agent.exe process that was
spawned by Battle.net, and then quickly launch Agent.exe manually (before
Battle.net spawns another one automatically). Repro is sporadic, but I'm able
to get it eventually if I try enough times (10+).
wine-5.12-64-ge0e3b6bc91 (Staging) [553c1cff]:
- No crashes in 20 manual retries
- 'Errors' directory in ProgramData is empty
wine-5.12-97-g262e4ab9e0 (Staging) [f6954e6e]:
- 4 crashes in 20 manual retries, plus 2 crashes of automatically spawned Agent
- 'Errors' directory already gets one entry just after starting Battle.net
I have attached logs with +seh,+ntdll,+relay,+timestamp from f6954e6e and from
Staging 5.13, and also some Agent crash reports.
All builds tested are with PE support.
--
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.
More information about the wine-bugs
mailing list