yuzu/yuzu-emu.github.io
1
0
Fork 0
mirror of https://github.com/yuzu-emu/yuzu-emu.github.io.git synced 2025-07-28 12:42:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update index.md

Browse source 
added some technical details (dangling objects)
This commit is contained in:
Honghoa 2021-08-10 13:55:56 -03:00 committed by GitHub
parent 47b6871fb0
commit c4235e5f7c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
site/content/entry/yuzu-progress-report-jul-2021/index.md
View file

@ -443,8 +443,8 @@ memory, even though the information became basically useless at this point.
One of the many jobs of the kernel in the OS is to keep track of all the resources available in the system.
For this reason, these dangling objects were a problem, as the kernel calculates the number of resources that can be spawned based partly on the number of active objects in
memory.
With dozens of different kernel objects being created thousands of times between emulation sessions, this easily saturated the amount of objects that could be spawned due to
yuzu hitting the resource limits much earlier than expected.
With dozens of different kernel objects being created thousands of times between emulation sessions, this easily saturated the amount of objects that could be spawned due to yuzu hitting the resource limits much earlier than expected.
What's more, since these objects stick around even after the emulation session is closed, this is a memory leak that would gradually increase for as long as the emulator is running a game — in other words, it would persist even if you stopped the emulation and started it again.
bunnei took a long look at the problem and improved the situation, but there's still ongoing work to make our implementation more robust and accurate.