mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-25 07:46:01 +03:00
[PR #2895] [MERGED] Core: Pooled Memory Fixes #3060
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#3060
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/shadps4-emu/shadPS4/pull/2895
Author: @StevenMiller123
Created: 5/10/2025
Status: ✅ Merged
Merged: 5/11/2025
Merged by: @squidbus
Base:
main← Head:pooled-memory-updates📝 Commits (10+)
4f1a8c5Update sceKernelMemoryPoolExpandf7aee88Update MemoryPoolReserve74bb0c1Don't coalesce PoolReserved areas.e434bc0Update PoolCommit1cca6c4Formatting33cb81bAdjust fixed PoolReserve path5a455c9Remove phys_base modifications21e8fb2Use VMAHandle.Contains()fdff2fcUpdate memory.cpp1dcdc53Remove unnecessary code📊 Changes
3 files changed (+110 additions, -64 deletions)
View changed files
📝
src/core/libraries/kernel/memory.cpp(+17 -10)📝
src/core/memory.cpp(+91 -53)📝
src/core/memory.h(+2 -1)📄 Description
This introduces a handful of bug fixes designed to make our memory pool implementation more hardware-accurate. All of these changes are based exclusively on hardware tests, so there may be some niche edge cases I've misinterpreted.
Changes:
Coalesce PoolCommitted memory- Removed change because of Windows.vma_mapcorruption introduced by #2080sceKernelMemoryPoolReservecalls withaddrIn = 0sceKernelMemoryPoolExpandwith the updated logic used bysceKernelAllocateDirectMemorysceKernelMemoryPoolExpanderrors when there's not enough space to expand.sceKernelMemoryPoolCommitaddress restrictions.This should address #1485, though it doesn't affect any games I own.
Unreal Engine games using memory pools seem to be unaffected by my changes.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.