MacOS Monterey raise fatal error on startup: Illegal threadstate encountered #8406
Assignees
Labels
bug
Bugs and errors
FAQ
Instructions to fix problems
linux / macos
support
Questions from users, help and support
Comments
|
It's a macos compatibility issue with used java version, not xmage. Your logs shows outdated java version:
|
|
@JayDi85 Thanks for the hints, somehow my java failed to automatically update for some time. Log from script: Log from launcher: |
|
Hmm... it looks like the JVM itself is crashing. I don't see any references to XMage code in those logs. I suspect you would have this problem with any Java program. Are you on x86 or ARM hardware? I know some of the newer Macs are ARM but have x86 emulation. It looks like your JVM is the x86 version. If you have ARM hardware, you should probably be using an ARM build of Java. I'm not much of a Mac guy though so if that's not the case I'm not sure what the problem is except that it looks like a bug in Java rather than anything we can fix. |
|
|
MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports) @JayDi85 |
|
It's a connection problem. Make sure that you use OpenJDK 8. Try again. XMage require a stable connection but some VPN or proxy services can call disconnect after few minutes -- so try to disable proxy/vpn. |
|
This is the monterey beta, right? The official release isn't out yet and it may be a bug. |
|
Also try a beta client with beta server: http://xmage.today/ (just unpack zip to any folder and run launcher). Beta server uses OpenJDK, so it can be more stable with OpenJDK clients. |
JayDi85
changed the title
|
@theelk801 it's RC1. I reported the issue to apple repeatedly, but haven't heard back so far. @JayDi85 I'm not running any proxy and my connection is pretty stable. I disabled antivirus software (just in case) and double-checked if there is anything in the OS options (they did not add anything regarding the network in privacy options). |
|
Can you run local server and play on it (from launcher)?
|
|
No, I'm getting the same JBoss error when trying to connect to the local server, both on released version and beta. |
|
Well. It's a java compatibility problem and must be reported to OpenJDK community. You can try to install latest java like java 11 or newer and run xmage from the run script in xmage folder -- if it was fixed in latest java versions then you will at least be able to play xmage with computer/AI. |
|
Thanks a lot for your help. I've reported the errors there let's see if they manage to fix it. |
|
I also am having this issue. |
|
Any news after macos updates? If it still fails then you can try new options (copy and insert it to the launcher settings -> java -> client):
|
|
There hasn't been any updates yet to Monterey. I did add the suggested options. Note the the Wurm Online Launcher also has similar issues with it Crashing. Once i nthe game if you can get it launched it is fine. So hopefully there will be a patch in Java to fix this. |
|
@JayDi85 what does that bit do? From what I'm reading above, this seems like an issue in Java or openjdk specifically. |
|
@cferdinandi it's a possible workaround for java apps with same errors. Found it on internet and it's not related to Monterey, but can be useful. |
|
Ah thanks! |
|
After some experimentation, I found out that OpenJDK 11.0.12 works best for me. |
|
@Averethel is there a way to force that version onto your machine? I have so far only ever used the installation instructions on the Xmage website. |
|
@cferdinandi If you're using homebrew it's available as Notably, you'd need to run xmage client via the script ( |
|
Also you can manually put java files from downloaded OpenJDK archive to |
|
@Averethel Homebrew FTW. Thank you so very much (and thank you to @JayDi85 for the launcher workaround). |
|
@cferdinandi Hi there i stumbled on this thread after updating my OS today. Now my xmage does not work as did yours. I am not familiar with code so i am hoping someone can walk me through getting my issue fixed. Would be much appreciated as xmage is the only thing i like to play on my mac. |
|
@MrLooper1977 hey there! I ended up not following the guidance above because...
|
|
Now that it's been mentioned, do you know if there's anything that needs to be done with regards to the log4j exploit? I did a search through the pom files and didn't see that we directly depend on log4j (though I might have missed it). I saw some comment that we had replaced log4j with another logger some time ago. I'm not sure how we find out if XMage is vulnerable to this or not but it does look like a pretty scary exploit from what I've read. |
|
I read elsewhere that Xmage does use log4j, but it appears that's no longer the case: #8512 In which case... ignore that last comment! Phew! |
|
Ah, didn't see those bug reports. Looks like we're all good then. |
|
Still no fix, huh? :( |
|
@MrLooper1977 I finally got this figured out, and wanted to share with you...
|
|
@cferdinandi Thanks so much, xmage is now up and running again. I really appreciate the reply. |
|
Woohoo! Now I'm just waiting for all of my images to redownload. Damn thing keeps timing out because my internet is too fast 😂😂😂 |
|
@cferdinandi i downloaded the images as a torrent file and then just place them in the image folder. You then have to download the images as normal for newer cards after the torrent was posted. I think I still have the file if you have some kind of drop box I can send it to. As I cannot find the link to where I originally found them. |
|
Ah that's very kind of you! I'm almost done now, but thanks so much! |
This was referenced Feb 11, 2022
Closed
|
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
XMage crashes constantly on macOS Monterey with the following error message:
Here's the contents of the generated error report:
If there is any more information I can provide to help with debugging, please let me know.
The text was updated successfully, but these errors were encountered: