Zones Restarting and deleting corpses!

[cubber]

Over the last 3 days of svn revisions around 340 on I have been having issues with zone restarts. For instance I have been hunting in seb with my monk and his bot group consisting of

1 cleric
1 shamy
1 ranger
1 wizard
1 rogue

after about a half hour of play the zone will restart and my client will hang. I can log back in cause the server does not crash just the zone. When I log back in my character is in the same spot he was in when the zone crashed and I can not summon any bots becuase they are already in the zone. So I log out and log back in and I can summon bots. At this point it is just annoying. But if I die it crashes the zone, and the kicker is when I log back in I am in the same spot of the zone where I died and crashed cept my character is naked and the corpse is deleted! I have to revert to backups to get my character back.

Stuff from the logs when it happens:

[Debug] [WORLD__ZONE] [9] [cabeast] ZoneToZone request for Nuggethead current zone 106 req zone 89

[Debug] [WORLD__ZONE] [9] [cabeast] Processing ZTZ for egress from zone for client CHARNAME

[Debug] [WORLD__ZONE] Found a zone already booted for CHARNAME

[Debug] [WORLD__ZONE] [11] [sebilis] ZoneToZone request for CHARNAME current zone 106 req zone 89

[Debug] [WORLD__ZONE] [11] [sebilis] Processing ZTZ for ingress to zone for client CHARNAME

[Debug] [WORLD__CLIENT] New connection from 192.168.42.6:47274
[Debug] [NET__IDENT_TRACE] 192.168.42.6:47274: First opcode 0x4dd0 did not match expected 0x2792
[Debug] [NET__IDENT_TRACE] 192.168.42.6:47274: Tried patch 6.2_world, and it did not match.
[Debug] [NET__IDENT_TRACE] 192.168.42.6:47274: First opcode 0x4dd0 did not match expected 0x2ec9
[Debug] [NET__IDENT_TRACE] 192.168.42.6:47274: Tried patch 6.2_zone, and it did not match.
[Debug] [NET__IDENT_TRACE] 192.168.42.6:47274: First opcode matched 0x4dd0 and length matched 464
[Debug] [NET__IDENTIFY] Identified stream 192.168.42.6:47274 with signature Titanium_world
[Debug] [WORLD__CLIENT] Checking inbound connection 192.168.42.6 against BannedIPs table
[Debug] [WORLD__CLIENT] Connection 192.168.42.6 PASSED banned IPs check.  Processing connection.
[Debug] [WORLD__CLIENT] ACCNTNAME: Logged in. Mode=(Zoning)
[Debug] [WORLD__CLIENT] ACCNTNAME: MiniLogin Account #1
[Debug] [WORLD__CLIENT] ACCNTNAME: Telling client to continue session.
Unable to get group id, char not found!
[Debug] [WORLD__CLIENT] ACCTNAME: Zoning to sebilis (89)
[Debug] [WORLD__CLIENT] ACCTNAME: Sending client to zone sebilis (89) at publicipaddress:7010
[Debug] [WORLD__ZONE] [11] [sebilis] Setting to 'sebilis' (89)
[Debug] [WORLD__CLIENT] ACCTNAME: Client disconnected (not active in process)
[Debug] [WORLD__ZONELIST] Removing zoneserver #11 at :7010
[Debug] [WORLD__ZONELIST] Hold Zones mode is ON - rebooting lost zone
[Debug] [WORLD__LAUNCH] zone: dynamic_10 reported state STOPPED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_10 reported state STARTED (2 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:43107
[Debug] [WORLD__CONSOLE] New zoneserver #14 from 127.0.0.1:43107
[Debug] [WORLD__ZONE] [14] Zone started with name dynamic_10 by launcher zone
[Debug] [WORLD__ZONE] [14] Auto zone port configuration.  Telling zone to use port 7013

this also was inside a crashlog file in my servers root directory.

Wed Feb 18 23:01:02 EST 2009 World crashed.

I have tried 3 revisions so far and all give me the same issue. I have also let a character sit pretty much idle in bazaar for 10 hrs with a cleric and shamy bot up with no crash. Crashes seem to happen always in combat, and on character death. Possibly bot death as well not sure though since I never can tell if a bot died and it caused a crash. I will test this.