SweetHome3D crash on start with Ubuntu 24.10 : library initialization failed - unable to allocate file descriptor table - out of memoryAbandon (core dumped)

This topic has been viewed 10531 times and has 4 replies
Thread status: Active
Questions about Sweet Home 3D installation [img]http://www.sweethome3d.com/images/flags/en_small.gif[/img]
Post Reply New Topic
Krakapuk
Posts: 2
Joined: Sat Nov 23, 2024 3:22 pm

SweetHome3D crash on start with Ubuntu 24.10 : library initialization failed - unable to allocate file descriptor table - out of memoryAbandon (core dumped)

Post by Krakapuk »

Hi
After a fresh install of Ubuntu 24.10, and download and install of SweetHome3D-7.5-linux-x64, I got this error :

Code: Select all

./SweetHome3D
library initialization failed - unable to allocate file descriptor table - out of memoryAbandon (core dumped)
The same problem occurs with the snap version of Sweethome3D 6.6 available in the Ubuntu app center:

Code: Select all

sweethome3d-homedesign
Picked up _JAVA_OPTIONS: -Duser.home=/home/xxxxxxxx/snap/sweethome3d-homedesign/15
library initialization failed - unable to allocate file descriptor table - out of memoryAbandon (core dumped)
Searching for this kind of error on web, it appears related to ulimit of java and recent changes in linux default limit for the number of open files...
However I did not find a clean way to manage the problem with Sweet Home 3D.

Help welcome :)
ts101
Posts: 1
Joined: Sun Dec 08, 2024 6:40 pm

Re: SweetHome3D crash on start with Ubuntu 24.10 : library initialization failed - unable to allocate file descriptor table - out of memoryAbandon (core dumped)

Post by ts101 »

In case anyone else stumbles upon this:

A workaround (?) for this problem is to manually set the "ulimit" to a number that works, e.g. open a shell run

Code: Select all

ulimit -n 10000

and then start SH3D from this shell.

Now, I have absolutely no clue of java and have no idea if it does anything else, so use on your own risk.

That said, it seems to only affect the shell it is run in as in another shell, when I run

Code: Select all

ulimit -n

it still returns "1024", as was the case in the shell I tried running SH3D from when it did give the error from the post above.
Krakapuk
Posts: 2
Joined: Sat Nov 23, 2024 3:22 pm

Re: SweetHome3D crash on start with Ubuntu 24.10 : library initialization failed - unable to allocate file descriptor table - out of memoryAbandon (core dumped)

Post by Krakapuk »

Many Thanks ts101, it works ! [B-)]

I confirm "ulimit -n 10000" seems to affect only the shell environment in which the command is run.
Indeed, closing the shell where Sweethome 3d was successfully launched, and reopening a new one without running "ulimit -n 10000", leads to the same error "library initialization failed..."
sjb007
Posts: 300
Joined: Tue May 18, 2021 1:49 pm

Re: SweetHome3D crash on start with Ubuntu 24.10 : library initialization failed - unable to allocate file descriptor table - out of memoryAbandon (core dumped)

Post by sjb007 »

Just add the ulimit command in your ~/.bashrc file, then it will apply for all shells.
User avatar
dorin
Posts: 824
Joined: Thu Apr 24, 2014 9:14 am
Country: Vatra Dornei, Suceava, Romania

Re: SweetHome3D crash on start with Ubuntu 24.10 : library initialization failed - unable to allocate file descriptor table - out of memoryAbandon (core dumped)

Post by dorin »

New Year, new computer and a fresh debian install.
1. With first system installation (stable) I don't have Wi-Fi connection.
So, I've switch to sid (Still In Development) and the Wi-Fi connection is UP.
2. Try to run SH3D:
- with double-click => nothing
- run in terminal =>

Code: Select all

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

2.1 I've added to ~.bashrc file

Code: Select all

ulimit -n 10000
with not remarkable effects.

2.2 I've added to every sh scripts SweetHome3D

Code: Select all

#!/bin/sh 
ulimit -n 10000
and solve the problem for SH3D to be launched in both situation.

3. Trying to launch from Eclipse as debug and I've receive again the error, this time in Eclipse console.

Solution (for me):
-run as root:

Code: Select all

echo > /etc/security/limits.d/systemd.conf "* hard nofile 65536"

-then RESTART!
It seems to work for me.

PS: I suspect it's related to java 8.
A computer program does what you tell it to do, not what you want it to do. Murphy's Law
When all else fails, read the instructions. Murphy's Law
If you don't like "AS IS", DIY. Dorin's law
Post Reply New Topic

Who is online

Users browsing this forum: No registered users and 1 guest