-
Notifications
You must be signed in to change notification settings - Fork 779
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
Client Freezes as Soon as it Starts up on MacOS #11292
Comments
If it freeze before you see a connection dialog then it's auto-connect problem. See here for the fix. |
@JayDi85 Not working for me: |
@SteffenJahr are you a topic starter? You must restart mac to apply new settings. If not helps then describe your problem with details:
|
@JayDi85 No i am not but I have the same issue. I launch the client, the ui shows up and immediately the color wheel appears and the app frezes. And I restarted my Mac several times.
|
Hi, OP here, that com.apple.java.util.prefs API isn't showing up on my end: This is where I get to before it freezes: For reference this is my Activity Monitor: Thank you for any help you can provide! |
Hey, did you solve this issue in any way? It looks like I have the same thing and I can't seem to fix it. |
Follow that instructions to replace xmage’s java with updated version - it must fix most problems: #8406 (comment) |
Hello,
sorry for getting back to you this late, sadly this has not worked - (I downloaded the newest Mac tar file and overwrote my Contents folder. Still the same issue of an unresponsive XMage Connect Screen.
I really appreciate the help though,
Have a great new year!
Gesendet: Freitag, 15. Dezember 2023 um 03:49 Uhr
Von: "Oleg Agafonov" ***@***.***>
An: "magefree/mage" ***@***.***>
Cc: "DeliriumXDHS" ***@***.***>, "Comment" ***@***.***>
Betreff: Re: [magefree/mage] Client Freezes as Soon as it Starts up on MacOS (Issue #11292)
Follow that instructions to replace xmage’s java with updated version - it must fix most problems: #8406 (comment)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Same issue. no autoconnect, updated the java version. Tiny detail is, it doesn't hang on startup directly, it hangs right after any interaction with the window (ie. clicking anywhere). |
Solutuion for users who raplaced java, but can't play on public servers -- now it can be compatible: #12768 |
- GUI: added non-blocking UI to almost all app and game dialogs; - GUI: it allows to switch between UI dialogs and use any UI elements at any moment; - GUI: it allows to use chat, card popup, battlefield, concede and other features while choosing (related to #12670); - GUI: it allows to download images while playing (related to #4160, not fully tested); - GUI: enabled by default, can be disabled by java option: -Dxmage.guiModalMode=true - connection: auto-connect will be visible in main menu on startup; - connection: removed some unused features (auto-connect by command line); - connection: added <ESC> button to close connection dialog; - download: added background images download (see non-blocking UI); - download: improved cancel stability and fixes that it can't stop preparing/downloading process in some use cases; - app: fixed freezes on macOS systems in some use cases (related to #12431, #11292, #9300, #4920);
Original problem was in wrong implementation of modal windows (xmage code for system events processing). Not actual anymore with non-blocking UI in last release #12825 |
So, I figured out that some other people were having the same issue I was on Mac which was basically some other program is interfering with Java so the client can't run properly.
What sucks though is that the replies are always "it must be Contexts or Magnet or something" I have neither of those apps, so I have no idea what it is that's conflicting with Xmage.
I could go and delete absolutely everything from my Activity Monitor but that would mean I'd have to do that every single time I wanna run Xmage, and since it's not a fast process it would render it virtually unusable anyways.
Anyone know how I can find out exactly what is clashing with the client so I can just shut that down? Thank you!
Related:
#4920
#5928
#6398
The text was updated successfully, but these errors were encountered: