`fuse: memory allocation failed` when running the AppImage

[Alfro]

I'm trying to run the app image on my distribution:

./TablePlus-x64.AppImage

Doing this, I get the following:

fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

even though other images seem to run correctly, I tried the fallback methods as shown in the AppImage docs here: https://docs.appimage.org/user-guide/troubleshooting/fuse.html#fallback-if-fuse-can-t-be-made-working

1. First I tried extracting the image using the given comment:

./TablePlus-x64.AppImage --appimage-extract

I got:

This doesn't look like a squashfs image.
Failed to open squashfs image

2. Then I tried mounting it:

sudo mount -o loop TablePlus-x64.AppImage mnt

I got:

mount: mnt: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

I get this on the dmesg:

[774011.064426] loop0: detected capacity change from 0 to 136892
[774011.067221] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[774011.067677] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[774011.067756] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[774011.068221] FAT-fs (loop0): bogus number of reserved sectors
[774011.068223] FAT-fs (loop0): Can't find a valid FAT filesystem
[774011.069283] ISOFS: Unable to identify CD-ROM format

3. Then I tried extracting it with bsdtar:

mkdir AppDir
cd AppDir
bsdtar xfp ../TablePlus-x64.AppImage

I got:

bsdtar: Error opening archive: Unrecognized archive format

Versions

• distro (lsb_release -a): Manjaro Linux 25.0.0 Zetar
• fuse (fusermount -V): fusermount version: 2.9.9
• AppImageLauncher (pacman -Q --info appimagelauncher): 2.2.0-10 https://github.com/TheAssassin/AppImageLauncher

[Alfro]

Apologies if this is the wrong place for this. I don't know if there's an issue with with the launcher or with this AppImage in particular, but since other AppImages seem to work on my system I thought it might be the later.

I don't know if it's related, but I saw this issue on the appimagelauncher project: TheAssassin/AppImageLauncher#361