Skip to content
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

library initialization failed - unable to allocate file descriptor table - out of memory #13029

Closed
StianOby opened this issue Oct 25, 2024 · 1 comment
Labels
linux / macos support Questions from users, help and support

Comments

@StianOby
Copy link

After upgrading from Ubuntu 24.04 to 24.10, I get the following error message trying to launch xMage:

INFO  2024-10-25 22:41:23,683 Starting MAGE CLIENT version: 1.4.54-V3 (build: 2024-09-25 12:58)                          =>[main] MageFrame.main 
INFO  2024-10-25 22:41:23,685 Java version: 1.8.0_201                                                                    =>[main] MageFrame.main 
INFO  2024-10-25 22:41:23,685 Logging level: INFO                                                                        =>[main] MageFrame.main 
INFO  2024-10-25 22:41:23,685 Default charset: UTF-8                                                                     =>[main] MageFrame.main 
INFO  2024-10-25 22:41:23,788 Custom (or bundled) Java certificate file (cacerts) file found                             =>[AWT-EventQueue-0] MageFrame.<init> 
library initialization failed - unable to allocate file descriptor table - out of memory

Googling turned up this old StackExchange thread: https://stackoverflow.com/questions/49435109/error-upon-jar-execution-unable-to-allocate-file-descriptor-table

And also this 4 month old reddit post about a user with a bleeding edge Debian system (likely comparable to Ubuntu 24.10) experiencing the same issue with a different .jar app: https://www.reddit.com/r/slaythespire/comments/1dgtkif/recent_trouble_launching_on_debian_resolved/

Unsure about how I can go about debugging this furhter, but very willing to do so if provided with instructions.

@JayDi85
Copy link
Member

JayDi85 commented Oct 25, 2024

Looks like that bug was fixed for later java versions (xmage uses java 8 201):
shot_241026_011002

So two workarounds possible:

  1. Limit OS resources by special ulimit -n 10000 command, see your link;
  2. Manually update launcher's java to newer version. You can try to use latest java 8 (no needs in additional settings -- just files replace in launcher/java folder) or any other java 9+ versions (see detailed instructions);

@JayDi85 JayDi85 added support Questions from users, help and support linux / macos labels Jan 1, 2025
@JayDi85 JayDi85 closed this as completed Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
linux / macos support Questions from users, help and support
Projects
None yet
Development

No branches or pull requests

2 participants