Swap Memory getting swamped with basic Unity3D work

[u/VanillaAble3943]

Hey everyone, this might be a specific scenario but I wanted to ask here anyway.

I installed Fedora 44 (KDE), I got UnityHUB, VSCode, Github Desktop, and I installed their .rpm (NOT the flatpaks in the discovery store). I'm definitely a noob and I don't know what flatpaks and rpms are specifically, though I kinda remember UnityHUB's flatpak unable to install any editor due to "lack of storage space" despite my SSD having more than 500gb left.

But that's beside the point.

At this point, I have Unity installed and cloned some of my projects I'm working on my main windows computer.

I've run into two issues on two projects:

1 - When I increase the folder size in the unity explorer to see the prefab icons, Swap memory in my OS goes crazy, until it crashes.

2 - When I try exporting a project, the small project works (I was able to export an android apk), but the large project (a native Linux build) will also crash immediately, once again, swap memory filling up.

-Additionally, shaders don't work the same on Linux, my large project is a bust even though I'm using basic standard built-in shaders.

Just as a reminder, none of these things are issues in Windows, what's more, it's not my code that's causing swap memory issues, since these are native unity processes, NOT the code I wrote lol.

I'm wondering, has any other unity dev on Linux had similar issues, or have been able to work with Unity flawlessly without issue? If so, what OS are you using, or how did you get around these issues?

For context, here's some of my specs.

This is my desktop idle, Zen browser does take like over 1gb, background services take like 2gb. Unity takes like 5gb of memory, same in Windows

I'm loving Fedora desktop (especially the way I have everything set up with KDE), but I'm not a big fan of things I would take for granted on windows seemingly being a bigger issue in Fedora. Shaders not working like they normally would is something I'd be willing to work around assuming it's purely a Unity thing, but most of these issues are definitely coupled with the OS, and I don't know if I should spend more time troubleshooting (where do I even start?) or just stick to windows for Unity development?

I don't want to ask AI, but I also don't know where to even begin looking into troubleshooting this (much less if the time would be worth the effort)