0.47.9 failed to launch: fuse: memory allocation failed

cursor 0.47.9
os: archlinux

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

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
Can't open squashfs image: Bad address

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
execv error: No such file or directory

it was working fine and the update prompted. and this happened.

7 Likes

Following, I’ve got the same issue…

1 Like

Same issue

1 Like

Sorry about this. It did not come up in our testing.

Which linux distro and version are you using? How much RAM do you have on your machines?

If you download the latest appimage from Downloads | Cursor - The AI Code Editor does it run?

I think that can helps:

I am using appimagelaucher on my ubuntu 24.04, that automatically create launcher for the new AppImage (with a prompt confirmation).

I removed it, then Cursor run without problem:

sudo apt remove --purge appimagelauncher
./Cursor-0.47.9-x86_64.AppImage

I would like it to run with my Appimagelauncher though like any other AppImage applications.

2 Likes

yeah, im using appimagelauncher too.

archlinux, latest. ram 256gb.

downloaded latest from the website

Same issue, manjaro. It’s ok before upgrading…I had to fallback to previouse version (I tried to uninstall appimageLauncher, still not work), below is the output while running .

./Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage                                                                                                                 1 ✘ 
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
Can't open squashfs image: Bad address

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
execv error: No such file or directory

@mikeluigijean solution worked. I uninstalled AppImageLauncher, and latest version of Cursor ran fine.

Bazzite 41, KDE Plasma 6, Wayland, 16GB RAM. Cursor AppImage file is straight from the site.

cursor 0.47.9
ubuntu 24.10, gnome, wayland
no AppImageLauncher

cursor running without problems

I feel like something has changed in the way Cursor handles his sandbox environnement in the last version as of now.

Can you try to temporary disable the restriction for unprivileged users?

sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

same issue ubuntu 22.04 64Gb ram i guess this is a Wayland issue

Came to report the same issue. Also using appimagelauncher. All other appimages work fine.

After executing the command, I got no such file or directory.

same issue

Same issue, if i try to start the Appimage i get this:


./Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage

/usr/bin/AppImageLauncher: /lib64/libcurl.so.4: no version information available (required by /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)

Squashfs image uses (null) compression, this version supports only xz, zlib.

ERROR: appimage_shall_not_be_integrated : sqfs_open_image error: /home/user/Applications/Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage

AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1)

Squashfs image uses (null) compression, this version supports only xz, zlib.

ERROR: appimage_is_terminal_app : sqfs_open_image error: /home/user/Applications/Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage

AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)

Squashfs image uses (null) compression, this version supports only xz, zlib.

ERROR: appimage_register_in_system : sqfs_open_image error: /home/user/Applications/Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage

which: no gtk-update-icon-cache-3.0 in (/home/user/.pyenv/plugins/pyenv-virtualenv/shims:/home/user/.pyenv/shims:/home/user/.pyenv/bin:/home/user/.local/bin:/home/user/.local/share/pnpm:/home/user/.krew/bin:/usr/lib64/ccache:/home/user/.cargo/bin:/home/user/.rover/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/var/lib/snapd/snap/bin:/home/user/go/bin:/home/user/.nsccli/bin:/home/user/.temporalio/bin:/home/user/.nsccli/bin)

which: no update-icon-caches in (/home/user/.pyenv/plugins/pyenv-virtualenv/shims:/home/user/.pyenv/shims:/home/user/.pyenv/bin:/home/user/.local/bin:/home/user/.local/share/pnpm:/home/user/.krew/bin:/usr/lib64/ccache:/home/user/.cargo/bin:/home/user/.rover/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/var/lib/snapd/snap/bin:/home/user/go/bin:/home/user/.nsccli/bin:/home/user/.temporalio/bin:/home/user/.nsccli/bin)

System:

➜  Applications cat /etc/os-release 
NAME="Fedora Linux"
VERSION="41 (Workstation Edition)"
RELEASE_TYPE=stable
ID=fedora
VERSION_ID=41
VERSION_CODENAME=""
PLATFORM_ID="platform:f41"
PRETTY_NAME="Fedora Linux 41 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:41"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f41/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=41
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=41
SUPPORT_END=2025-12-15
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Update to the latest Alpha Version of appimagelauncher worked:

3 Likes

This solved the issue for me. However, I feel disabling AppArmor is not the best solution. How can I create an exception only for Cursor to run?

thank you, this solve my issue.

The -git version of appimagelauncher from AUR solved it from me.

Thank you all. :ok_hand: