SphereServer BugTracker - SphereServer
View Issue Details
0001849SphereServerexecutable - linux buildpublic01-11-10 22:3414-12-14 21:39
wuffel 
Ben 
normaltweaksometimes
closedno change required 
20-09-2009, 0.56b Prerelease 
 
Automated (specify build number)
UseNetworkMulti
None
0001849: ClientCrash + "incorrect" errormessage
Sometimes, my Client and one of another person crashes. the third person, near us, has never problems.
21:29:WARNING:12:Client crashed at 0,0,0,0: 0x3133392E (30.104.164, 7.0.8.2)
21:29:WARNING:14:Client crashed at 0,0,0,0: 0x3139322E (168.1.108, 7.0.8.2)

IPadresse isn't correct, and the crashposition is also not that cool. ;)

Actually i have no idea how to get the reason of the crash.
No tags attached.
Issue History
01-11-10 22:34wuffelNew Issue
01-11-10 22:40TerrikateNote Added: 0000739
01-11-10 23:26wuffelNote Added: 0000740
04-11-10 12:09MrSugarCubeNote Added: 0000743
05-11-10 20:39wuffelNote Added: 0000751
14-11-10 19:54MrSugarCubeCategoryexecutable - linux => executable - linux build
03-12-10 02:05MrSugarCubeNote Added: 0000773
14-12-14 21:39BenNote Added: 0002590
14-12-14 21:39BenStatusnew => closed
14-12-14 21:39BenAssigned To => Ben
14-12-14 21:39BenResolutionopen => no change required

Notes
(0000739)
Terrikate   
01-11-10 22:40   
The third person throws anything to the ground?
(0000740)
wuffel   
01-11-10 23:26   
Unfortunately not. Sometimes an item has been moved before, or a normal ".tile-command" was executed. the only common: always the same two clients are crashing.
(0000743)
MrSugarCube   
04-11-10 12:09   
I've fixed the error message formatting, but the information it shows probably isn't going to be that useful for finding the cause of the crash.

A packet log might indicate if the crash is triggered by a particular packet.
(0000751)
wuffel   
05-11-10 20:39   
Crash, with the following log-entry:

19:36:WARNING:11:Client crashed at 0,0,0,0: 0xC0000005 CRASH @ 0x2F525017 (client.exe, 7.0.8.2)
(0000773)
MrSugarCube   
03-12-10 02:05   
If this still happens on the latest automated build then we'll need more information on how to reproduce it, since the client crash message isn't really that useful (and doesn't necessarily indicate that it's a Sphere issue).

If there isn't any specific action that can reproduce the crash then a packet log might help identify if it's caused by a particular packet.
(0002590)
Ben   
14-12-14 21:39   
error message was fixed a while back.