#197 outstanding crash bug in solo HO code

クローズ
4 年 前image によって開かれました · 1 コメント
image4 年 前 にコメントしました

Unfortunately the try/catch code stopped us from capturing the tracing. However seems given the writelock that the Solo HO code is to blame.

14:45:50 E Zone      : Exception while running 'FrostfangSea'

14:45:50 I Player    : Player 'Honkhonkjones' (330) data saved.

14:45:50 I Player    : Saving character history, type = XP (3) subtype = Adventure (1)

14:45:50 I Player    : Saving character history, type = XP (3) subtype = Adventure (1)

14:45:50 I Player    : Saving character history, type = XP (3) subtype = Adventure (1)

14:45:50 I Player    : Saving character history, type = XP (3) subtype = Adventure (1)

14:45:50 I Zone      : Scheduling client 'Honkhonkjones' for removal.
[Thread 0x7fffc573f700 (LWP 1051) exited]

14:45:51 I Packet    : OP_OutOfSession

14:46:01 E Mutex     : Possible deadlock attempt by 'SpellProcess::MSpellProcess'!

14:46:06 D World     : Removing connection...

14:46:13 E Mutex     : The mutex SpellProcess::m_soloHO called from Process at line 229 timed out waiting on another writelock!

14:46:13 E Mutex     : The following functions had locks:

14:46:13 E Mutex     : CastProcessedSpell, number of locks = 1

14:46:24 E Mutex     : The mutex SpellProcess::m_soloHO called from Process at line 229 timed out waiting on another writelock!

14:46:24 E Mutex     : The following functions had locks:

14:46:24 E Mutex     : CastProcessedSpell, number of locks = 1

14:46:35 E Mutex     : The mutex SpellProcess::m_soloHO called from Process at line 229 timed out waiting on another writelock!

14:46:35 E Mutex     : The following functions had locks:

14:46:35 E Mutex     : CastProcessedSpell, number of locks = 1

14:46:46 E Mutex     : The mutex SpellProcess::m_soloHO called from Process at line 229 timed out waiting on another writelock!

14:46:46 E Mutex     : The following functions had locks:

14:46:46 E Mutex     : CastProcessedSpell, number of locks = 1
Unfortunately the try/catch code stopped us from capturing the tracing. However seems given the writelock that the Solo HO code is to blame. ``` 14:45:50 E Zone : Exception while running 'FrostfangSea' 14:45:50 I Player : Player 'Honkhonkjones' (330) data saved. 14:45:50 I Player : Saving character history, type = XP (3) subtype = Adventure (1) 14:45:50 I Player : Saving character history, type = XP (3) subtype = Adventure (1) 14:45:50 I Player : Saving character history, type = XP (3) subtype = Adventure (1) 14:45:50 I Player : Saving character history, type = XP (3) subtype = Adventure (1) 14:45:50 I Zone : Scheduling client 'Honkhonkjones' for removal. [Thread 0x7fffc573f700 (LWP 1051) exited] 14:45:51 I Packet : OP_OutOfSession 14:46:01 E Mutex : Possible deadlock attempt by 'SpellProcess::MSpellProcess'! 14:46:06 D World : Removing connection... 14:46:13 E Mutex : The mutex SpellProcess::m_soloHO called from Process at line 229 timed out waiting on another writelock! 14:46:13 E Mutex : The following functions had locks: 14:46:13 E Mutex : CastProcessedSpell, number of locks = 1 14:46:24 E Mutex : The mutex SpellProcess::m_soloHO called from Process at line 229 timed out waiting on another writelock! 14:46:24 E Mutex : The following functions had locks: 14:46:24 E Mutex : CastProcessedSpell, number of locks = 1 14:46:35 E Mutex : The mutex SpellProcess::m_soloHO called from Process at line 229 timed out waiting on another writelock! 14:46:35 E Mutex : The following functions had locks: 14:46:35 E Mutex : CastProcessedSpell, number of locks = 1 14:46:46 E Mutex : The mutex SpellProcess::m_soloHO called from Process at line 229 timed out waiting on another writelock! 14:46:46 E Mutex : The following functions had locks: 14:46:46 E Mutex : CastProcessedSpell, number of locks = 1 ```
image4 年 前 にコメントしました
共同編集者
should potentially be addressed by http://cutpon.com:3000/devn00b/EQ2EMu/commit/103859462dad8c0f2e87e3c3de9a9690c866f3cd
image 4 年 前 に閉じられました
会話に参加するには サインイン してください。
読み込み中…
キャンセル
保存
まだコンテンツがありません