 Issue Information
Issue Information
				- 
						
						#005441 
- 
								
								
								0 - None Assigned 
- 
								
								
								Done 
 Issue Confirmations
Issue Confirmations
					- 
							Yes (1)No (0)
 0
 0
 
					
							
					Map Server Crashes on status_change_timer mismatch
Posted by Hercules Bot on 14 March 2012 - 04:14 AM
					
								
									
								
									
								
									
								
								Originally posted by kroxt
Since [rev=15686]
I'm using Champion after attacking some monsters this error shows at the server logs.
							
							Since [rev=15686]
I'm using Champion after attacking some monsters this error shows at the server logs.
status_change_timer: Mismatch for type 93: 47 != 655371
												Originally posted by kroxt
												
											
										
#0  ers_obj_alloc_entry (self=0xb7b7486c) at ers.c:191
	 ret = (void *) 0xb
	 __FUNCTION__ = "ers_obj_alloc_entry"
#1  0x080a6706 in status_change_start (bl=0xcfb3178, type=SC_COMBO, rate=10
    val1=263, val2=<value optimized out>, val3=<value optimized out>, val4=
    tick=301, flag=0) at status.c:7926
	 sd = (struct map_session_data *) 0xcfb3178
	 sc = (struct status_change *) 0xcfb341c
	 sce = (struct status_change_entry *) 0x0
	 status = (struct status_data *) 0xcfb33c8
	 vd = (struct view_data *) 0xcfb335c
	 opt_flag = 0
	 calc_flag = 0
	 undead_flag = 0
	 val_flag = 0
	 tick_time = <value optimized out>
	 __FUNCTION__ = "status_change_start"
	 types = {SC_AUTOGUARD, SC_DEFENDER, SC_REFLECTSHIELD, SC_ENDURE}
#2  0x08105850 in skill_attack (attack_type=1, src=0xcfb3178, dsrc=0xcfb317
    bl=0xac537c84, skillid=263, skilllv=5, tick=4267068379, flag=0) at skil
	 flag = 1
	 sce = <value optimized out>
	 dmg = {damage = 508, damage2 = 0, type = 0, div_ = 3, amotion = 538
  dmotion = 384, blewcount = 0, flag = 273, dmg_lv = ATK_DEF}
	 sstatus = (struct status_data *) 0xcfb33c8
	 tstatus = (struct status_data *) 0xac537e6c
	 sc = (struct status_change *) 0xac537ec4
	 sd = (struct map_session_data *) 0xcfb3178
	 tsd = (struct map_session_data *) 0x0
	 type = 8
	 damage = 508
	 rdamage = 0
	 __FUNCTION__ = "skill_attack"
#3  0x08153728 in battle_weapon_attack (src=0xcfb3178, target=0xac537c84,
    tick=4267068379, flag=0)
at battle.c:4021
	 triple_rate = 25
	 sd = (struct map_session_data *) 0xcfb3178
	 tsd = (struct map_session_data *) 0x0
	 sstatus = (struct status_data *) 0xcfb33c8
	 tstatus = (struct status_data *) 0xac537e6c
	 sc = (struct status_change *) 0x0
	 tsc = (struct status_change *) 0xac537ec4
	 damage = <value optimized out>
	 rdamage = <value optimized out>
	 rdelay = <value optimized out>
	 skillv = 5
	 wd = {damage = -1, damage2 = -1074308232, type = 182, div_ = 1, amotion = 1,
  dmotion = -1074308232, blewcount = 134535323, flag = 135849849, dmg_lv = 2328}
	 __FUNCTION__ = "battle_weapon_attack"
#4  0x0816fc2e in unit_attack_timer (tid=22, tick=4267068379, id=2000758, data=0)
    at unit.c:1773
	 bl = (struct block_list *) 0xcfb3178
#5  0x0817cb30 in do_timer (tick=4267068405) at timer.c:371
	 tid = 22
	 diff = -26
	 __FUNCTION__ = "do_timer"
#6  0x08179e94 in main (argc=1, argv=0xbff75ce4) at core.c:264
	 next = <value optimized out>
												
												
												Originally posted by sizenine
I confirm receiving those errors in r15689 as I've posted here with many test case updates:
http://rathena.org/b...server-crashes/
However, those skills are not the cause of the map server crashes I'm 99% sure (was deceiving me too). But this bug report I have posted here is actually the cause of the map server crashes:
http://rathena.org/b...tax-is-applied/
												
											
										I confirm receiving those errors in r15689 as I've posted here with many test case updates:
http://rathena.org/b...server-crashes/
However, those skills are not the cause of the map server crashes I'm 99% sure (was deceiving me too). But this bug report I have posted here is actually the cause of the map server crashes:
http://rathena.org/b...tax-is-applied/
												Originally posted by Ind
I wasn't able to reproduce, make sure it happens on latest svn (as i've done a few fixes earlier that could have fixed this)
												
											
										I wasn't able to reproduce, make sure it happens on latest svn (as i've done a few fixes earlier that could have fixed this)
												Originally posted by kroxt
Ok thank you. I'll test it on r15728.
												
											
										Ok thank you. I'll test it on r15728.
												Originally posted by Ind
No new info in months, archiving.
												
											
										No new info in months, archiving.













