Chrome gets killed after a few days and can't be restarted (Segmentation fault)

Post bug reports related to either the kiosk ISO or the kiosk wizard here.
smock
White ninja
White ninja
Posts: 7
Joined: 22 Aug 2022, 08:50
Distribution: Porteus Kiosk 5.4.0

Chrome gets killed after a few days and can't be restarted (Segmentation fault)

Post#1 by smock » 23 Mar 2023, 06:36

Dear forum

I have another little issue with Porteus Kiosk 5.4.0 apart of Porteus Kiosk hangs up after a few days: After a few days Chrome ends randomly and I observe the following:
  • PC does only show the wallpaper image then
  • gui-app script continuously tries to restart Chrome
  • this fills up disk with browser metrics
  • browser window does not reappear forever
Manually freeing up disk space and deletion of user data (/home/guest/.config, /home/guest/.cache) does not help.

Starting Chrome interactively (using su - guest -c "chrome URL") brings "Segmentation fault" to the console and Chrome ends again immediately. Enabled debug-logging (--enable-logging --v=1), chrome_debug.log does not show any errors.

Reboot of the PC fixes the issue.

Does anybody have an idea how to identify the root cause of this? Any hint is much appreciated.

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5660
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Chrome gets killed after a few days and can't be restarted (Segmentation fault)

Post#2 by fanthom » 23 Mar 2023, 07:21

Could be a RAM problem or GPU driver issue.

Please use:

Code: Select all

gpu_driver=modesetting
you may also enable free trial of the updates service and check if latest kernel/Xorg/mesa resolve the problem.

If you use 'persistence=full' then please disable it as the problem may be also caused by unreliable storage device (USB stick, SD card).

Thanks
Please add [Solved] to your thread title if the solution was found.

Post Reply