Games freezing after a few seconds
Started by FAZZA




8 posts in this topic
FAZZA
Unregistered


 
09-05-2015, 02:46 PM -
#1
all the time i getting this
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
any tips?
its at the start of my games but each time at a different point
tambre
Unregistered


 
09-05-2015, 03:05 PM -
#2
(09-05-2015, 02:46 PM)FAZZA Wrote: all the time i getting this
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
any tips?
its at the start of my games but each time at a different point

Please read the FAQ. RPCS3 does not run commercial games and you should actually post the full log, ensure that you're on the latest version of master and post your settings (this only applies until PR#1205 gets merged).
flashmozzg
Unregistered


 
09-05-2015, 06:06 PM -
#3
(09-05-2015, 03:05 PM)tambre Wrote:
(09-05-2015, 02:46 PM)FAZZA Wrote: all the time i getting this
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
any tips?
its at the start of my games but each time at a different point

Please read the FAQ. RPCS3 does not run commercial games and you should actually post the full log, ensure that you're on the latest version of master and post your settings (this only applies until PR#1205 gets merged).

This error has been appearing rather frequently in many games lately. It happens with recompiler but I'm not sure it's exclusive to this (sometimes game just hang with this error and needs restart), maybe it's just more likely to trigger the cause. It's definitely new issue and somewhat recent issue.
tambre
Unregistered


 
09-05-2015, 07:44 PM -
#4
(09-05-2015, 06:06 PM)flashmozzg Wrote:
(09-05-2015, 03:05 PM)tambre Wrote:
(09-05-2015, 02:46 PM)FAZZA Wrote: all the time i getting this
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
any tips?
its at the start of my games but each time at a different point

Please read the FAQ. RPCS3 does not run commercial games and you should actually post the full log, ensure that you're on the latest version of master and post your settings (this only applies until PR#1205 gets merged).

This error has been appearing rather frequently in many games lately. It happens with recompiler but I'm not sure it's exclusive to this (sometimes game just hang with this error and needs restart), maybe it's just more likely to trigger the cause. It's definitely new issue and somewhat recent issue.

I could look into developing a test, that triggers this behaviour. Could you name a couple games, where this behaviour is present? Though I'm rather busy with the development of ESN, I surely could find time.
Nekotekina
RPCS3 Developer


0
137 posts 5 threads Joined: Aug 2017
09-05-2015, 09:41 PM -
#5
It's not an issue at all. This error is normal behaviour of this function.

I guess freezes are completely unrelated.
flashmozzg
Unregistered


 
09-05-2015, 11:38 PM -
#6
(09-05-2015, 07:44 PM)tambre Wrote:
(09-05-2015, 06:06 PM)flashmozzg Wrote:
(09-05-2015, 03:05 PM)tambre Wrote:
(09-05-2015, 02:46 PM)FAZZA Wrote: all the time i getting this
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
E {PPU[0x5c] Thread (vdispStart)[0x00015ce0]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)
any tips?
its at the start of my games but each time at a different point

Please read the FAQ. RPCS3 does not run commercial games and you should actually post the full log, ensure that you're on the latest version of master and post your settings (this only applies until PR#1205 gets merged).

This error has been appearing rather frequently in many games lately. It happens with recompiler but I'm not sure it's exclusive to this (sometimes game just hang with this error and needs restart), maybe it's just more likely to trigger the cause. It's definitely new issue and somewhat recent issue.

I could look into developing a test, that triggers this behaviour. Could you name a couple games, where this behaviour is present? Though I'm rather busy with the development of ESN, I surely could find time.

I caught it a lot (like 1 out of 5) during start up of disgaea 3 with llvm recompiler.
tambre
Unregistered


 
09-06-2015, 07:46 AM -
#7
(09-05-2015, 11:38 PM)flashmozzg Wrote:
(09-05-2015, 07:44 PM)tambre Wrote:
(09-05-2015, 06:06 PM)flashmozzg Wrote:
(09-05-2015, 03:05 PM)tambre Wrote: Please read the FAQ. RPCS3 does not run commercial games and you should actually post the full log, ensure that you're on the latest version of master and post your settings (this only applies until PR#1205 gets merged).

This error has been appearing rather frequently in many games lately. It happens with recompiler but I'm not sure it's exclusive to this (sometimes game just hang with this error and needs restart), maybe it's just more likely to trigger the cause. It's definitely new issue and somewhat recent issue.

I could look into developing a test, that triggers this behaviour. Could you name a couple games, where this behaviour is present? Though I'm rather busy with the development of ESN, I surely could find time.

I caught it a lot (like 1 out of 5) during start up of disgaea 3 with llvm recompiler.

Does it happen with interpreter? As far as I've tested, LLVM recompiler has plenty of bugs and isn't as accurate as interpreter, so that might be the cause, if those errors happen only on the recompiler.
flashmozzg
Unregistered


 
09-06-2015, 01:37 PM -
#8
(09-06-2015, 07:46 AM)tambre Wrote: Does it happen with interpreter? As far as I've tested, LLVM recompiler has plenty of bugs and isn't as accurate as interpreter, so that might be the cause, if those errors happen only on the recompiler.

Can't say for certain right now. But this error ir rather recent and didn't happen before.
Nekotekina
RPCS3 Developer


0
137 posts 5 threads Joined: Aug 2017
09-06-2015, 05:43 PM -
#9
Morons.


Forum Jump:


Users browsing this thread: 1 Guest(s)