0.47.9 failed to launch: fuse: memory allocation failed

tuananh · March 24, 2025, 1:34pm

so this is a bug in appimagelauncher?

0xSharp · March 24, 2025, 3:01pm

Possibly, but the latest stable version was released almost five years ago, so it’s more likely a bug in libfuse or one of its dependencies

By the way, I just noticed that libfuse released a new version an hour ago—maybe it fixes the issue…

ianchanning · March 24, 2025, 3:54pm

Great plan. It worked.

Notes from me for Pop OS (Ubuntu 22.04):

I can’t remember how I first install AppImageLauncher (guess is via deb)
What worked was downloading the appimagelauncher_3.0.0-alpha-4-gha253.36951ec_amd64.deb, this opens up the Eddy window where you can uninstall the existing version
You have to uninstall before installing this alpha
Installing the deb then ran fine
After installing it I went back to my ~/Applications directory and I could immediately run the ./Cursor-0.47.9-x86_64... file

ianchanning · March 24, 2025, 4:24pm

I created a GitHub with notes about the v3.0.0-alpha4 solution:

github.com/TheAssassin/AppImageLauncher

Unable to run the Cursor v0.49.7 AppImage on Ubuntu 22.04 due to a FUSE-related error (fixed with v3.0.0-alpha-4).

opened 04:16PM - 24 Mar 25 UTC

ianchanning

bug needs verification

### Pre-submit checks - [x] I [checked for similar issues](https://github.com/T…heAssassin/AppImageLauncher/issues?q=) beforehand, but could not find any, not even closed ones. I could not add my bug report to any existing issue. - [x] I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise. ### Describe the bug **Note: this bug is fixed in [v3.0.0-alpha-4](https://github.com/TheAssassin/AppImageLauncher/releases/tag/v3.0.0-alpha-4), but I'm adding this here in case people come searching** I get the below error when running the latest version of Cursor v0.47.9. Quite a few others have this issue: https://forum.cursor.com/t/0-47-9-failed-to-launch-fuse-memory-allocation-failed/68394 In that forum [this post](https://forum.cursor.com/t/0-47-9-failed-to-launch-fuse-memory-allocation-failed/68394/18?u=ianchanning) shows the solution of using v3.0.0-alpha-4. - The AppImage file is not corrupted; I have verified its integrity. - I have tried running it from both the terminal and by double-clicking, with the same result. - If there's any other information needed, please let me know. ### Expected behavior I expected it to run and open Cursor. This is the first issue I have had updating Cursor, til now it has worked beautifully 🙏 ### Steps to reproduce the issue 1. I ran the Application via the Applications menu (nothing happens) 2. I tried deleting all the existing instances of Cursor and re-running a newly downloaded AppImage 3. I checked the file permissions: Ensured the AppImage has execute permissions: ``` -rwxrwxr-x 1 charp charp 173799928 Mar 24 16:41 Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage ``` 4. I tried running again: Attempted to run the AppImage again, but the error persists. 5. AppImageLauncher correctly installs it into the `~/Applications` directory, but if you run it via bash from there it gives the following error: ```sh $ ./Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage 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 ``` I also got this error when running the downloaded `AppImage` file (which first opens through AppImageLauncher) and clicking 'Run once': ```sh ./Cursor-0.47.9-x86_64.AppImage (AppImageLauncher:214844): GLib-CRITICAL **: 16:42:22.724: g_file_test: assertion 'filename != NULL' failed fuse: memory allocation failed ``` ### Screenshots ![Image](https://github.com/user-attachments/assets/228864e0-06d2-4d7f-924f-dc25613156d4) ### Distribution and desktop environment ## System Information - **Distribution:** Distributor ID: Pop Description: Pop!_OS 22.04 LTS Release: 22.04 Codename: jammy - **Kernel Version:** - `Linux charpie 6.12.10-76061203-generic #202412060638~1740154617~22.04~b4b3ebc SMP PREEMPT_DYNAMIC Fri F x86_64 x86_64 x86_64 GNU/Linux` - **FUSE Installation:** ```sh $ dpkg -l | grep fuse ii fuse3 3.10.5-1build1 amd64 Filesystem in Userspace (3.x version) ii fuseiso 20070708-3.2build1 amd64 FUSE module to mount ISO filesystem images ii gvfs-fuse 1.48.2-0ubuntu1 amd64 userspace virtual filesystem - fuse server ii libfuse2:amd64 2.9.9-5ubuntu3 amd64 Filesystem in Userspace (library) ii libfuse3-3:amd64 3.10.5-1build1 amd64 Filesystem in Userspace (library) (3.x version) ii libsquashfuse0:amd64 0.1.103-3 amd64 FUSE filesystem to mount squashfs archives library charp@charpie:~$ dpkg -l | grep fuse ii fuse3 3.10.5-1build1 amd64 Filesystem in Userspace (3.x version) ii fuseiso 20070708-3.2build1 amd64 FUSE module to mount ISO filesystem images ii gvfs-fuse 1.48.2-0ubuntu1 amd64 userspace virtual filesystem - fuse server ii libfuse2:amd64 2.9.9-5ubuntu3 amd64 Filesystem in Userspace (library) ii libfuse3-3:amd64 3.10.5-1build1 amd64 Filesystem in Userspace (library) (3.x version) ii libsquashfuse0:amd64 0.1.103-3 amd64 FUSE filesystem to mount squashfs archives library ``` ### Installed AppImageLauncher version v2.2.0 ### List of AppImages you tried - Only Cursor-0.47.9-x86_64.AppImage https://www.cursor.com/ ### Additional context _No response_

mutaphore · March 25, 2025, 4:58am

Tried to run Cursor v0.49.7 AppImage using v3.0.0-alpha-4 AppImageLauncher on my Ubuntu 24.04, but all I got back was a Nodejs terminal?

tmm1 · March 25, 2025, 5:11am

This is resolved in 0.48.1 which is available under Early Access

BanAnanas · March 28, 2025, 2:45pm

Is there a way to get older AppImages? Yes-> Downloads | Cursor - The AI Code Editor

system · April 27, 2025, 2:46pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Cursor-0.47.9-x86_64 Linux AppImage Invalid/Corrupt Bug Reports	2	140	April 26, 2025
Most recent Linux x64 AppImage is broken Bug Reports	3	505	May 1, 2025
Recent AppImages are not working: Squashfs image uses (null) compression, this version supports only xz, zlib, Ubuntu 22 Bug Reports	1	520	April 24, 2025
Why is so s#!t to install cursor on ubuntu 24.04.2? Discussions	3	512	February 22, 2025
Issue to install Cursor on a fresh Ubuntu 24.04 Bug Reports	15	12167	April 7, 2025

0.47.9 failed to launch: fuse: memory allocation failed

Related topics