mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-25 15:56:00 +03:00
[GH-ISSUE #3849] [GAME BUG]: Memory leak or VRAM explosion? #1154
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#1154
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?
Originally created by @wycGTX on GitHub (Dec 2, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3849
Checklist (we expect you to perform these steps before opening the issue)
Describe the Bug
Game Name : Bloodborne™ The Old Hunters Edition
I tried the methods I found online for similar issues, like increasing virtual memory, lowering the resolution, and applying various patches to reduce memory (VRAM) accumulation, but nothing worked. I had no choice but to come here for help. This save file already has 40 hours of playtime, and it would be really frustrating to give up now...
Reproduction Steps
After loading the save, the game crashes on the description screen and fails to start.
You can enter the game with a new or old save file, but only the save file with (Character Name: L) cannot access the game.
SPRJ0005.zip
Specify OS Version
Windows10 Professional 22H2
CPU
AMD Ryzen 7 5700X
GPU
Radeon™ RX Vega 56
Amount of RAM in GB
16
Amount of VRAM in GB
8
Log File
shad_log.txt
@RuskyDed commented on GitHub (Dec 2, 2025):
Look for the issue on your side. I was able to load your save without a problem.
@wycGTX commented on GitHub (Dec 2, 2025):
Can the save file for character L also successfully enter the game? Could you please let me know the version of the emulator you are using and your computer specifications? I am using the pre-release version 2025.12.1 e5f9280
@RuskyDed commented on GitHub (Dec 2, 2025):
I'm using the latest pre-release, 16G RAM + 16G Page file, 6G VRAM, the rest of it shouldn't matter.
As for the save: yes, L character loads fine at the Mensis Nightmare lamp.
@wycGTX commented on GitHub (Dec 2, 2025):
Okay, thank you for your reply. It seems I can only check for issues on my end.
@GHU7924 commented on GitHub (Dec 2, 2025):
@wycGTX
What version of Windows do you have? I see it's 10 Pro, but which edition? 22H2? I'm not sure, but that could have had an impact on something as well.
You are also missing modules.
Also your log has an error at the end:
@StevenMiller123 commented on GitHub (Dec 2, 2025):
While Bloodborne is known to have vram issues, your problem is different.
That assert in your log shows your GPU drivers are crashing. With Bloodborne, we usually only see this from modded games, though it could also be related to how old AMDs drivers for Vega GPUs are, or due to other issues with your device.
We generally don't provide support for hardware configurations a vendor stops supporting, especially for older hardware like your GPU.
@wycGTX commented on GitHub (Dec 3, 2025):
@RuskyDed @StevenMiller123
I re-extracted the game once. At first, it still didn’t work, but later I lowered the resolution to 720p and 30Hz, and I was able to enter the game. In the early stages of the game, there will be a group of monsters that release a full-screen AOE attack that hits both enemies and allies at the beginning, and it’s continuous. Every time they use this skill, I feel a slight lag, and it’s worse when there are more monsters. I don’t know if this increases the load on the graphics card or causes memory (VRAM) accumulation. However, when the character moves to a scene outside the monsters’ line of sight, I removed the limitations and played the game at 1080p, 60Hz until completion without encountering any issues. So I think the cause of the issue may be due to memory (VRAM) not being released in time. Of course, this is just my guess, and the actual impact should be determined by the log files.