Critical console exceptions

[coruja747]

using latest build 2587 (24 nov 2015) on my live server I'm getting tons of console errors, already tried to take a look at these codes but I don't find nothing wrong. So I will copy/paste here in case if someone want help fix it

the error 1 seems to be the most critical, it keep hours spamming the console at each second, making my daily sphere log file jump from 1mb to 20mb. Errors 2, 3 and 4 just appear a few times and stop in a few seconds

---

ERROR 1:

04:51:DEBUG:__ thread (15848) __ | # | _____ function _____________ | ticks passed from previous function start ______
04:51:DEBUG:>> 15848 | 0 | CWorld::OnTick | +0
04:51:DEBUG:>> 15848 | 1 | CSector::OnTick | +78
04:51:DEBUG:>> 15848 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
04:51:DEBUG:>> 15848 | 3 | CChar::OnTickEquip | +0
04:51:DEBUG:>> 15848 | 4 | CChar::Memory_OnTick | +0
04:51:DEBUG:>> 15848 | 5 | CChar::Memory_Fight_OnTick | +0
04:51:DEBUG:>> 15848 | 6 | CChar::Memory_Fight_Retreat | +0
04:51:DEBUG:>> 15848 | 7 | CVarDefMap::GetKey | +0
04:51:CRITICAL:Assert pri=2:'purecall' file 'unknown', line 1, in SUB: CChar::Char::Ticking items()

---

ERROR 2:

00:41:DEBUG:__ thread (15848) __ | # | _____ function _____________ | ticks passed from previous function start ______
00:41:DEBUG:>> 15848 | 0 | CWorld::OnTick | +0
00:41:DEBUG:>> 15848 | 1 | CSector::OnTick | +31
00:41:DEBUG:>> 15848 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
00:41:DEBUG:>> 15848 | 3 | CChar::OnTickStatusUpdate | +0
00:41:DEBUG:>> 15848 | 4 | CClient::UpdateStats | +0
00:41:DEBUG:>> 15848 | 5 | CClient::addManaUpdate | +0
00:41:DEBUG:>> 15848 | 6 | CPartyDef::AddStatsUpdate | +0
00:41:CRITICAL:"Access Violation" (0xf5ec8), in CChar::Tick() #1 "update stats"

---

ERROR 3:

00:48:DEBUG:__ thread (15848) __ | # | _____ function _____________ | ticks passed from previous function start ______
00:48:DEBUG:>> 15848 | 0 | CWorld::OnTick | +0
00:48:DEBUG:>> 15848 | 1 | CSector::OnTick | +31
00:48:DEBUG:>> 15848 | 2 | CChar::OnTick | +16 <-- exception catch point (below is guessed and could be incorrect!)
00:48:DEBUG:>> 15848 | 3 | CChar::OnTickStatusUpdate | +0
00:48:DEBUG:>> 15848 | 4 | CClient::UpdateStats | +0
00:48:DEBUG:>> 15848 | 5 | CClient::addStamUpdate | +0
00:48:DEBUG:>> 15848 | 6 | CPartyDef::AddStatsUpdate | +0
00:48:DEBUG:>> 15848 | 7 | CChar::CanSee | +546
00:48:DEBUG:>> 15848 | 8 | CPointBase::GetDistSight | +0
00:48:CRITICAL:"Access Violation" (0xf5ec8), in CChar::Tick() #5 "update stats"

---

ERROR 4:

15:10:DEBUG:__ thread (30636) __ | # | _____ function _____________ | ticks passed from previous function start ______
15:10:DEBUG:>> 30636 | 0 | CWorld::OnTick | +0
15:10:DEBUG:>> 30636 | 1 | CSector::OnTick | +15
15:10:DEBUG:>> 30636 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed an
d could be incorrect!)
15:10:DEBUG:>> 30636 | 3 | CChar::Skill_Done | +0
15:10:DEBUG:>> 30636 | 4 | CChar::Skill_Stage | +0
15:10:DEBUG:>> 30636 | 5 | CChar::Skill_Magery | +0
15:10:DEBUG:>> 30636 | 6 | CChar::Spell_CastDone | +0
15:10:DEBUG:>> 30636 | 7 | CVarDefMap::Empty | +0
15:10:CRITICAL:"Access Violation" (0xdad47), in CChar::Tick() #2 "timer expired"

[coruja747]

another exception that randomly occour even without players online and always crash the sphere:

14:05:DEBUG:__ thread (7032) __ | # | _____ function _____________ | ticks passed from previous function start ______
14:05:DEBUG:>> 7032 | 0 | CWorld::OnTick | +0
14:05:DEBUG:>> 7032 | 1 | CSector::OnTick | +16
14:05:DEBUG:>> 7032 | 2 | CChar::OnTick | +0
14:05:DEBUG:>> 7032 | 3 | CItem::OnTrigger | +1513937
14:05:DEBUG:>> 7032 | 4 | CResource::ResourceGetDef | +0
14:05:DEBUG:>> 7032 | 5 | CResourceBase::ResourceGetDef | +0 <-- exception catch point (below is guessed and could be incorrect!)
14:05:WARNING:Forcing thread 'Main' to terminate...

[coruja747]

since a long time ago I don't get any of these errors anymore and sphere is totally stable reaching 30d+ uptime, so I think we must consider it fixed