jhorv

Reducing Memory Allocations 202305

16

**TL;DR:** this PR reduces LOH memory allocations by 47% in one test scenario This PR focuses on reducing memory allocations, especially by eliminating large object heap (LOH) allocations caused by...

ServerBase thread safety

9

@lostromb [commented](https://github.com/Ryujinx/Ryujinx/pull/4537#issuecomment-1477130450) on closed PR #4537 about an intermittent exception when stopping emulation. This PR fixes some issues I found while investigating, and though I was unable to reproduce @lostromb's...

Ryujinx.Ava: fixes for random hangs on exit

3

I've experienced a lot of instances recently where Ryujinx.Ava would hang on exit, sometimes for so long that I'd open up Task Manager and kill it. It was always with...

Fix crash in SettingsViewModel when Vulkan isn't available

2

Fixes #4984 Doesn't make Ryujinx work on Win11 on ARM, because after this it crashes in ARMeilleure.

Add support to IVirtualMemoryManager for zero-copy reads

8

I am reworking PR #4777 into 3 or 4 new PRs. This is 1 of X and its main features are: - `IVirtualMemoryManager` impls of `GetWritableRegion()` use pooled memory when...

Refactor memory managers to a common base class, consolidate Read() method logic

1

This PR refactors the various memory managers to share a common abstract base class for the purpose of improving code reuse and consolidating similar implementations of algorithms like virtual-to-physical memory...

New pooled memory types

4

This PR adds 2 new types for using pooled memory: - `MemoryOwner` is a generic class for easy access to pooled memory. - `SpanOwner` is generic value type (`readonly ref...

replace ByteMemoryPool usage in Ryujinx.HLE

1

Replaces use of `ByteMemoryPool` with the new `MemoryOwner` and `SpanOwner` types in the Ryujinx.HLE project. It does use `SpanOwner` in 2 places to make those fully allocation-less, but otherwise these...

Replace passing by IMemoryOwner<byte> with passing by concrete MemoryOwner<byte>

3

Replaces cases where `MemoryOwner` is passed/returned as `IMemoryOwner`. Also, changes locations that were getting a `Span` to the memory via `MemoryOwner.Memory.Span` to use `MemoryOwner.Span` directly, which is cleaner and more...