[Bug]: Crash on hover tooltip in Linux

[notlet]

Preflight checklist

• I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• I have searched the frequently asked questions for a solution that fixes this problem, without success.
• I have checked that I'm using the latest stable version of the app.

What app version are you using?

5.5.6

What operating system version are you using?

Linux

Expected Behavior

No response

Actual Behavior

When hovering over anything with a tooltip, the app starts to jitter and output GPU errors in logs, then turns fully white or gray, and then crashes. This happens on both the AppImage version and on the self-compiled RPM version I'm using. Everything works as expected when --in-process-gpu flag is added.

2024-10-24.15-25-23.mp4

(exactly the same thing happens on the official AppImage so I don't feel the need to record another video)

---

System info:
Fedora 40, GNOME 46 on Wayland, Nvidia RTX 4060 Mobile GPU

Screenshots

No response

[ThaUnknown]

I mean, LMAO linux

don't really know what to tell you here, this is a native tooltip, just like in chrome, it's something that I in no way control, so all I can say is good luck figuring it out? if you're curious for finding related issues, try looking for "html title attribute crashes" or smth along those lines

[notlet]

ok fair lmao
if its not anything custom i guess its fully electron's fault
i remember it didn't even want to launch on wayland without --no-sandbox flag, but now it does and idk what happened to make it work again

sidenote: do you mind providing an rpm package? i dont like appimages so i compile it as an rpm myself, but adding it officially would be nice and as easy as copying the deb config but replacing deb with rpm

[ThaUnknown]

if everything works fine with --in-process-gpu then simply this issue is to be closed, from what I've been told by people more experienced with linux gpu fuckery, it means ur gpu config is bad in some way

no, feel free to PR that urself

[ThaUnknown]

might be fixed in latest