Ciao,

I did not notice the link in the previous link. I got the PharoDebug.log file.
It is very big because there are a lot of traces there.

The last one is the following.
Does it correspond to your crash?

Yes, 12 December 2018 6:47.......... 6:xxx

it's the time when I started having problems

To be sure, you could rename this file and try to run again your image to see if we have logs.

OK.

I rename the file.

When i Launch the corrupt image the system don't create the new PharoDebug.log

As this point ( but maybe it happened even before )

when from PharoLauncher on the corrupt image

i select the Show in folder menu option

the shell report:

(nautilus:17273): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed

(nautilus:17273): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed

(nautilus:17273): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(nautilus:17273): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:17273): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

Thanks,

Dario

P.S. In the /etc/sysctl.conf i add this entry ( can they somehow interfere? )

kernel.shmmax=6442450944

kernel.shmall=1572864