|
l2jserver
|
ffebdd285d
BETA: GameTimeController AIOOBE fix. I didnt got any problems again, but who knows, maybe they dont occur on plain test servers. Also, Im using TIntObjectHashMap with ReentrantLock instead of the custom one, just because here we need to read and write at the same time (iterate and remove) and if this is done via L2TIntObjectHashMap, you will pretty much get a deadlock (readlock has locked the iteration process and while iterating we remove an object, a writelock is called, but in order to proceed, the writelock waits the readlock to unlock... so you get pretty much infinite wait.)
|
13 éve |
Nik
ffebdd285d
BETA: GameTimeController AIOOBE fix. I didnt got any problems again, but who knows, maybe they dont occur on plain test servers. Also, Im using TIntObjectHashMap with ReentrantLock instead of the custom one, just because here we need to read and write at the same time (iterate and remove) and if this is done via L2TIntObjectHashMap, you will pretty much get a deadlock (readlock has locked the iteration process and while iterating we remove an object, a writelock is called, but in order to proceed, the writelock waits the readlock to unlock... so you get pretty much infinite wait.)