Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: AppImage constant Javascript exception #7646

Closed
1 task done
mahlonsmith opened this issue Feb 14, 2025 · 4 comments
Closed
1 task done

[bug]: AppImage constant Javascript exception #7646

mahlonsmith opened this issue Feb 14, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@mahlonsmith
Copy link

mahlonsmith commented Feb 14, 2025

Is there an existing issue for this problem?

  • I have searched the existing issues

Operating system

Linux

GPU vendor

Nvidia (CUDA)

GPU model

RTX 4060

GPU VRAM

16GB

Version number

5.6.2

Browser

Firefox 135

Python dependencies

No response

What happened

Jumped from 5.3.0 to 5.6.2 this morning, using the AppImage running for the first time. Getting near constant alerts with an identical backtrace:

Image

What you expected to happen

The alert seems to happen any time there's a new log line displayed within the Invoke AppImage UI.

How to reproduce the problem

Additional context

No response

Discord username

No response

@mahlonsmith mahlonsmith added the bug Something isn't working label Feb 14, 2025
@psychedelicious
Copy link
Collaborator

Rather vague error 🤔

Does disk at /tmp/ have free space?

What Linux distro?

@mahlonsmith
Copy link
Author

Yeah, very. :(

Plenty of space at /tmp:

❯ df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
tmpfs            47G  108M   47G   1% /tmp

This is Ubuntu 24.10. I am running lots of other AppImages (Krita, LM-Studio, Obsidian, etc) without issue. Running with --no-sandbox.

@mahlonsmith
Copy link
Author

Okay, not sure why this would matter, but I think I can make this happen now regularly, and more importantly, avoid it from happening. I am running the AppImage from the command line, then backgrounding it.

If I leave it in the terminal foreground, it's fine.

I just tried the same thing with Obsidian, and am getting a very similar message, so it seems specific to signal handling with the AppImage -- not specifically Invoke related. I think we can probably close this.

@psychedelicious
Copy link
Collaborator

Funny - I was searching for more info on this error and saw some issues on an Obsidian repo with the same message but wasn't sure if it related to Invoke.

Based on your findings, I agree that this is probably not something we are going to make meaningful progress on from our side, so I'll go close this. Thanks for that detective work and getting (close) to the bottom of it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants