This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
cellsync issue
#2
(01-20-2016, 02:16 PM)Ekaseo Wrote:
Quote:·E {PPU Thread[0x1] (main_thread)[0x003746b8]} cellSync: cellSyncMutexTryLock() -> CELL_SYNC_ERROR_BUSY (0x8041010a)

it shows this error while in dragon ball z and in afterburner climax... any idea why there is this error? or is it something not implemented yet :/

Mostly for debugging purposes, it would seem. Mutex (Mutual Exclusion) is used for synchronization between threads, to ensure that no two processes are in their critical section at the same time.

I'm not very proficient, but a thread likely tries to lock the mutex, but CELL_SYNC_ERROR_BUSY is returned, because the mutex is locked already. Probably not really a bug or anything, rather just expected behaviour.
Reply


Messages In This Thread
cellsync issue - by Ekaseo - 01-20-2016, 02:16 PM
RE: cellsync issue - by tambre - 01-20-2016, 04:03 PM
RE: cellsync issue - by Ekaseo - 01-20-2016, 04:42 PM
RE: cellsync issue - by tambre - 01-20-2016, 05:03 PM
RE: cellsync issue - by Nekotekina - 01-20-2016, 08:43 PM
RE: cellsync issue - by Kristiqn5 - 01-20-2016, 09:07 PM
RE: cellsync issue - by Nekotekina - 01-21-2016, 12:18 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)