Possible memory management issues.

[Spidy123222]

I notice when I try running programs that don't particularly need much memory like fex running steam and SB cosmic shake running (4gb ram required for game which also works fine on a 2gb gpu). It quickly runs out of memory on 16gb unified memory m2 pro MacBook Pro under asahi Linux using gnome.

I've tried utilizing swap and it doesn't seem to get utilized enough (never used 1/8th of the 16gb swap). I'm wondering if muvm is having issues in this manner sharing its memory to the host.

Is this the right area to post such report? I just use GitHub and discord for bug reports.

[slp]

muvm configures the VM to use a maximum of ~80% of the RAM available in the system. If the game is not expected to use that much memory, it's likely that what's consuming memory it's the filesystem cache in the guest. #89 should drastically improve this behavior.

[Spidy123222]

muvm configures the VM to use a maximum of ~80% of the RAM available in the system. If the game is not expected to use that much memory, it's likely that what's consuming memory it's the filesystem cache in the guest. #89 should drastically improve this behavior.

I was thinking of testing this. How could I test the branch on the system? I know I need to compile via rust. By doing a cargo build release.

[Spidy123222]

The mentioned pull request was merged but doesn't seem to help for this situation. This is an image of memory usage over time. It doesn't use swap until very end and is a game that doesn't use too much ram. But it does here.

Couldn't screen record as it would crash OBS once it hits the problem.

This would also happen launching EA launcher from trying to run a EA game like burnout paradise remastered.