Crash at exit and RAM never freed while running a game

[Revision18]

Only tested PkMn Shield so far.

Two days ago, the game crashed after three hours. Today, I decided to run the game with System Monitor in another screen. This way, I can check if I'm running out of system resources.

I noticed the following: RAM is never freed. It starts allocating less than 10 GiB of RAM and then escalates to 13 GiB of RAM. This takes many hours, I'm not sure how many, around 3. At that point, I save and restart Yuzu, as a way to prevent a crash during an important moment of the game.

Installed Yuzu using Flatpak on Linux Ubuntu.

Log file compressed by 7zip. Renamed as .zip to satisfy github requirements.

inxi -v3 output:

System:
  Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A 
  Desktop: Gnome 3.36.9 Distro: Ubuntu 20.04.3 LTS (Focal Fossa) 
Machine:
  Type: Desktop Mobo: ASRock model: H81M-ITX 
  serial: <superuser/root required> UEFI [Legacy]: American Megatrends 
  v: P2.30 date: 03/17/2016 
CPU:
  Topology: Quad Core model: Intel Core i7-4790 bits: 64 type: MT MCP 
  arch: Haswell rev: 3 L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 57587 
  Speed: 3998 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 972 2: 1833 
  3: 1019 4: 1303 5: 1201 6: 1201 7: 1200 8: 1598 
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
  vendor: XFX Pine driver: amdgpu v: kernel bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.13 driver: amdgpu 
  resolution: 1600x900~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.40.0 
  5.11.0-46-generic LLVM 12.0.0) 
  v: 4.6 Mesa 21.0.3 direct render: Yes 
Network:
  Device-1: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: ASRock 
  driver: alx v: kernel port: d000 bus ID: 03:00.0 
  IF: enp3s0 state: up speed: 100 Mbps duplex: full
Drives:
  Local Storage: total: 2.27 TiB used: 2.00 TiB (87.8%) 
Info:
  Processes: 487 Uptime: 5h 37m Memory: 15.57 GiB used: 3.19 GiB (20.5%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 

yuzu_log.7z.zip

[Revision18]

More info: I reached the last city in the game. RAM usage when you respawn in this city is the most heavy of all the game maps so far.

As soon as I enter a house, speak to NPCs, then exit. My 16 GIB of RAM is filled up in System Monitor. Then system starts to use swap space, but the emulator crash and exit. This doesn't require many hours of play. Not for this city. Just start game, enter house, exit. Reproducible 100% of the time.

I think this is what is happening: the game never unloads previous map. They stay in memory. I don't know if this is an emulator issue or a game issue. I will have to test other games.

[Revision18]

More Info:

I ran flatpak update

Yuzu updates shown in list.

Now I can enter and exit houses in last city. Ram stays at 9 GiB.

Did any of you change something related to this?

I switched to Vulkan graphics options. But I did that before updating with flatpak and things remained the same. So I guess the update did something.

[Revision18]

More Info:

I spoke to soon. The RAM is doing same as before. It always goes up, never down, but slowly. It starts with lees than 10 GiB and it lets you play some hours.

I think some of my actions, like changing to vulkan or download update from flatpak, resulted in some cache getting cleared.

But at least the game can be played until the very end. Last city can be explored.

[FernandoS27]

More info: I reached the last city in the game. RAM usage when you respawn in this city is the most heavy of all the game maps so far.

As soon as I enter a house, speak to NPCs, then exit. My 16 GIB of RAM is filled up in System Monitor. Then system starts to use swap space, but the emulator crash and exit. This doesn't require many hours of play. Not for this city. Just start game, enter house, exit. Reproducible 100% of the time.

I think this is what is happening: the game never unloads previous map. They stay in memory. I don't know if this is an emulator issue or a game issue. I will have to test other games.

Could you be more specific?

[liushuyu]

Hi, are you still experiencing this issue in the latest version?