Hi Lockal, from the stacktrace it looks like a null pointer's being dereferenced in tr_sessionLock()'s call to "tr_lockLock (session->lock);" ... however, session->lock is initialized on startup and then never changed until shutdown. So maybe the crash reporter tool got confused with which report it sent with your summary, or maybe there's some memory corruption going on that NULLed that pointer out.
Hi Lockal, from the stacktrace it looks like a null pointer's being dereferenced in tr_sessionLock()'s call to "tr_lockLock (session->lock);" ... however, session->lock is initialized on startup and then never changed until shutdown. So maybe the crash reporter tool got confused with which report it sent with your summary, or maybe there's some memory corruption going on that NULLed that pointer out.
Lockal, are you able to reproduce this bug?