-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Freeze at 'Loading Magic Online' after sign-in #160
Comments
I cannot reproduce it here... Maybe give a try to |
Thanks for the patch. Unfortunately, I get the same behavior on pr157, different address in the log (full logs attached below). Is there any info I can provide that would help debugging? (Flags I can set to enable verbose logs, etc.)
|
You can add the |
0370:err:sync:RtlpWaitForCriticalSection section 00D1D040 "?" wait timed out in thread 0370, blocked by 030c, retrying (60 sec) I'm getting the same thing as well. I've tried the 4-3 image and the 2019 panard images, as well as test, debug, and update. I've also tried panard/mtgo:pr157 |
Reran with --debug enabled. Notable things from the logs: The following appears in the log upon loading.
The message 'No interface for {...]' repeats a lot, and after a while we see the following:
And so on. After the first 'RtlpWaitForCriticalSection', we stop seeing 'No interface for {...}'. We only see 'RtlpWaitForCriticalSection' repeat, for as long as I left the app running. Full logs attached: |
Also running into this issue, on two separate computers (both Fedora 36) |
This comment was marked as outdated.
This comment was marked as outdated.
Yes tried that on both machines, still have the issue after |
Also tried enabling the emulate desktop setting in winecfg, but same problem. Using |
I'm also also having the similar issues, attached are the --debug logs from running as both --test and not. When running normally, it sometimes freezes on the loading screen immediately after logging in, and sometimes freezes on the loading magic online page. When running with --test it always makes it to the loading magic online screen. The specific log attached from the non-test run was one freezing on the earlier loading screen. |
This comment was marked as outdated.
This comment was marked as outdated.
The instructions you referenced in the link aren't available any more for linux, but I installed using Lutris and applied the EULA fix necessary. This installation doesn't seem to suffer from the freezing issue. EDIT: On second/third run of that install, ran into the freeze again |
This comment was marked as outdated.
This comment was marked as outdated.
On my side, doing the following helps quite consistently, however, it feels slower:
Also note that doing
(enabling 2 CPUs) Using taskset also workaround the issue when using wine directly (outside docker). If this fixes the issue for most of you, I'll incorporate the change in the docker image, the time that either a new MTGO release is out, or we figure out why there is a threading issue within wine (a nightmare to debug).. EDIT:
adventurous users may try enabling more CPUs (e.g., |
eventually spat out after 'Loading Magic Online'
This worked to at least load the game but froze when trying to go to Collection.
|
That's interesting and shows a potential bug in MTGO.exe which might explain the freezes. Not sure why you don't have this error with the other command though...
|
Adding extra CPUs seems to help for me EDIT: Higher success rate, but still some freezing it seems |
after the latest update the cpuset fix does not work anymore |
I was having this problem as well. The below Thanks for all the work on this project.
|
Whenever I fully uninstall MTGO and reinstall, the application works fine on the first run. Second and subsequent runs all suffer from hanging after login. |
Since the daybreak transition, I'm no longer experiencing the freeze after login. |
I can confirm I am still experiencing the freeze after login with the newest script. Was also experiencing it in the version before the newest version.
|
@Greginator the latest |
Apologies this was an issue my end. Running
I don't know if leaving this for a long enough time would cause the hang to end, but I never even get that retrying message when I set it --limit-cpus to 2. |
New issue started presenting after today's MTGO update (2022/09/11). After signing in, application freezes at 'Loading Magic Online' dialog. Logs show the following:
====== MTGO.exe has started.
0324:err:sync:RtlpWaitForCriticalSection section 00D1D070 "?" wait timed out in thread 0324, blocked by 0264, retrying (60 sec)
0324:err:sync:RtlpWaitForCriticalSection section 00D1D070 "?" wait timed out in thread 0324, blocked by 0264, retrying (60 sec)
0324:err:sync:RtlpWaitForCriticalSection section 00D1D070 "?" wait timed out in thread 0324, blocked by 0264, retrying (60 sec)
0324:err:sync:RtlpWaitForCriticalSection section 00D1D070 "?" wait timed out in thread 0324, blocked by 0264, retrying (60 sec)
0324:err:sync:RtlpWaitForCriticalSection section 00D1D070 "?" wait timed out in thread 0324, blocked by 0264, retrying (60 sec)
0324:err:sync:RtlpWaitForCriticalSection section 00D1D070 "?" wait timed out in thread 0324, blocked by 0264, retrying (60 sec)
And so on.
Since it began appearing after today's magic online update I would suspect it's surfaced by a change in MTGO; I don't have enough experience with Wine to speculate about the root cause.
Attaching full log:
loading-screen-forever-20220901.txt
The text was updated successfully, but these errors were encountered: