mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-25 15:56:00 +03:00
[GH-ISSUE #675] Deleted #163
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#163
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 @Emulator-Team-2 on GitHub (Aug 30, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/675
@roamic commented on GitHub (Aug 30, 2024):
I have investigated and consulted with the team and it seems to be because of unstable TLS instructions patching on Windows.
@rafael-57 commented on GitHub (Sep 1, 2024):
These TLS instructions seem to be the cause of issue #687. I've had a person on Linux try and warp on BB to reproduce the issue. He warped 12 times and the emulator never hanged.
On Windows you can get hangs even on the first warp. You almost always get hang by the third or 4th warp. And the error is TLS malloc.
@voguelike commented on GitHub (Sep 1, 2024):
i tested my personal build just now and surprisingly found no TLS malloc errors and i'm still freezing indefinitely on warp. i've always had the TLS malloc error whenever this happened previously.
instead i now sometimes only have errors with

[Lib.Rtc] <Error> rtc.cpp:sceRtcGetCurrentClockLocalTime:80: (STUBBED) called [Lib.Rtc] <Error> rtc.cpp:sceRtcGetTick:122: (STUBBED) called [Lib.Rtc] <Error> rtc.cpp:sceRtcSetTick:191: (STUBBED) calledand
[Render.Vulkan] <Error> tile_manager.cpp:TryDetile:389: Unsupported tiled image: R32Sfloat (Depth_MacroTiled)@Ishikudeska commented on GitHub (Sep 1, 2024):
ok so we're at a graphical issue
hmmmm. TLS issue should still be looked into, but I was already guessing it was a problem graphically aswell
@voguelike commented on GitHub (Sep 1, 2024):
nevermind sorry, false alarm. i just had async logs from an unconfigured shadps4 user 😅