SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002362SphereServerexecutable - windows buildpublic12-06-14 06:3406-08-14 05:11
ReporterCoruja 
Assigned ToBen 
PrioritynormalSeveritymajorReproducibilityunable to reproduce
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version0.56c Nightly 
Nightly VersionAutomated (specify build number)
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Summary0002362: Strange "Divide by Zero" exceptions on latest builds
DescriptionI have no idea how to debug/reproduce to this, but I updated my live server from may 25 build to jun 11 build and now I'm getting tons of console exception. Already tried using jun 12 build too but the problem persists

on my test server I dont get even a single error, but on live server I got tons of errors :/
Steps To Reproduce
Additional Information13:47:DEBUG:__ thread (8284) __ | # | _____ function _____________ | ticks passed from previous function start ______
13:47:DEBUG:>> 8284 | 0 | CWorld::OnTick | +0
13:47:DEBUG:>> 8284 | 1 | CSector::OnTick | +16
13:47:DEBUG:>> 8284 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
13:47:DEBUG:>> 8284 | 3 | CChar::Death | +0
13:47:DEBUG:>> 8284 | 4 | CVarDefMap::Empty | +0
13:47:CRITICAL:"Integer: Divide by Zero" (0x2ead3), in CChar::Tick() 0000001 "death"
13:47:DEBUG:__ thread (8284) __ | # | _____ function _____________ | ticks passed from previous function start ______
13:47:DEBUG:>> 8284 | 0 | CWorld::OnTick | +0
13:47:DEBUG:>> 8284 | 1 | CSector::OnTick | +15
13:47:DEBUG:>> 8284 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
13:47:DEBUG:>> 8284 | 3 | CChar::Death | +0
13:47:DEBUG:>> 8284 | 4 | CVarDefMap::Empty | +0
13:47:CRITICAL:"Integer: Divide by Zero" (0x2ead3), in CChar::Tick() 0000001 "death"
13:47:DEBUG:__ thread (8284) __ | # | _____ function _____________ | ticks passed from previous function start ______
13:47:DEBUG:>> 8284 | 0 | CWorld::OnTick | +0
13:47:DEBUG:>> 8284 | 1 | CSector::OnTick | +0
13:47:DEBUG:>> 8284 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
13:47:DEBUG:>> 8284 | 3 | CChar::Death | +0
13:47:DEBUG:>> 8284 | 4 | CVarDefMap::Empty | +0
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
12-06-14 06:34CorujaNew Issue
13-06-14 03:51FeehNote Added: 0002294
13-06-14 04:17CorujaNote Added: 0002296
19-06-14 05:51kn4tsebNote Added: 0002302
17-07-14 00:49FeehNote Added: 0002335
05-08-14 04:06CorujaNote Added: 0002385
06-08-14 05:11BenStatusnew => resolved
06-08-14 05:11BenFixed in Version => 0.56c Nightly
06-08-14 05:11BenResolutionopen => fixed
06-08-14 05:11BenAssigned To => Ben

Notes
(0002294)
Feeh   
13-06-14 03:51   
What is the frequency it happens? (tons = console constant flood?)
There is any known abnormal side effect?
Any specific code that is executed during some char death?

As you stated, in my fresh test server I was not able to reproduce
(0002296)
Coruja   
13-06-14 04:17   
some ppl told me about NPCs which doesnt die. The NPC reach HITS=0 but stay alive and frozen without die, probably it's something related to this because the console error tell something about CChar::Tick() 0000001 "death"

I cant reproduce it here too, just found this huge error on logs. Normally my log files have 800kb/day and using this build I got 23mb/8hrs. Visually it's something about 50~100 errors each minute
(0002302)
kn4tseb   
19-06-14 05:51   
i have presented this issue, im using jun 12th revision, and i ve seen it with some npcs with large HP ranges, about more than 3000 max HP.... they die but its more like the npc freezes without dying, and console shows lots tick errors for some time... a few minutes even.. best way to solv it is by removing the npc with .remove command or wait till it finally becomes a corpse..
(0002335)
Feeh   
17-07-14 00:49   
Is this still happening?
If yes, any way reproduce the error or still unknown?
What flags are you using?
(0002385)
Coruja   
05-08-14 04:06   
Fixed on test build 1991