Hello There, Guest! Register

Demon's Souls [BLES00932] freezes but music and ambience continue playing
#1
After playing for a few minutes (up to maybe half an hour) Demon's Souls will hang (world, graphics, interface stops), but the music and ambient sounds will continue playing. At this point rpcs3 itself is not frozen, and I can end the emulation via its menus. Resizing the window doesn't resize the contents (https://prnt.sc/ousw24). In the attached log, less than two minutes passed before it froze and I hit Stop.

OS: Windows 10
CPU: i7-8086K, stable (tested with 12h+ Prime95)
RAM: 16Gb
GPU: Gigabyte 1080 (436.02)
Renderer: Vulkan
rpcs3: Tested various but current one is 0.0.6-8574-eed32cf3 (8603 did not seem to boot the game)

CPU settings: https://prnt.sc/owpaqh
GPU settings: https://prnt.sc/owpaty

Everything is at defaults except for Write Color Buffers. Multithreaded RSX is disabled. I've tried with Preferred SPU Threads: 2 and gotten the same results.

SPU decoders: it happens with ASMJIT, LLVM and Interpreter (fast). (Precise interpreter too slow to reliably test.)
PPU decoders: it happens with the LLVM recompiler but from what I could tell not with Interpreter (fast). (as above)

This is with a clean environment, no old caches from older versions. It happens with both with and without the 60 fps patch.

(Mods: if this doesn't get approved, please let me know what's missing so I can fix and resubmit it)

edit: attachment


Attached Files
.gz   RPCS3.log.gz (Size: 800.04 KB / Downloads: 4)
Reply
#2
I have the same issues, my next post is what I've found
Reply
#3
I've run into the same issues as you, on an extremely similar system-
OS: Windows 10
CPU: i7-8700K @4.9Ghz
RAM: 32GB @2400Mhz
GPU: EVGA GTX 1070 (431.36)
Renderer: Vulkan
rpcs3: Tested on every build from 8568-8612

From what I've gathered from reading my own logs (with sceNp: Fatal), the emulator loops the following output (on my end, at least) until emulation is stopped:
Code:
·W 0:03:11.667207 {PPU[0x1000017] Thread (NexusRevolution Main) [0x01d54f74]} sys_lwmutex: _sys_lwmutex_create(lwmutex_id=*0xd02687f0, protocol=0x2, control=*0xd0268a20, has_name=0x80000001, name=0xd0268a10)
·W 0:03:11.667236 {PPU[0x1000017] Thread (NexusRevolution Main) [0x01d54f74]} sys_lwmutex: _sys_lwmutex_create(lwmutex_id=*0xd0268750, protocol=0x2, control=*0xd02689f0, has_name=0x80000001, name=0xd0268a18)
·W 0:03:11.667254 {PPU[0x1000017] Thread (NexusRevolution Main) [0x01d55218]} sys_lwmutex: _sys_lwmutex_destroy(lwmutex_id=0x95063800)
·W 0:03:11.667270 {PPU[0x1000017] Thread (NexusRevolution Main) [0x01d55218]} sys_lwmutex: _sys_lwmutex_destroy(lwmutex_id=0x95063700)


I've attached my personal log from the run above to this replay, although it did have sceNp: Fatal on in order to make it easier to find whatever was looping.


Attached Files
.gz   RPCS3 (1).log.gz (Size: 824.25 KB / Downloads: 0)
Reply
#4
Is there anything I can do to help debug this?


(08-29-2019, 05:53 PM)kingcailan Wrote: I've attached my personal log from the run above to this replay, although it did have sceNp: Fatal on in order to make it easier to find whatever was looping.

You have to press the Add Attachment button too or the log file will only be selected, not uploaded.
Reply
#5
Quote:You have to press the Add Attachment button too or the log file will only be selected, not uploaded.

Thanks for the tip. Uploaded.
Reply
#6
I've tested various settings, and can now conclude after successfully leaving it alone for well over 24 hours total that it doesn't seem to freeze with TSX instructions disabled.

So there's something with TSX and these processors that makes it softlock.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)