| Anonymous | Login | Signup for a new account | 19-04-25 20:12 CEST |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |
| 0001849 | SphereServer | executable - linux build | public | 01-11-10 22:34 | 14-12-14 21:39 | |
| Reporter | wuffel | |||||
| Assigned To | Ben | |||||
| Priority | normal | Severity | tweak | Reproducibility | sometimes | |
| Status | closed | Resolution | no change required | |||
| Platform | OS | OS Version | ||||
| Product Version | 20-09-2009, 0.56b Prerelease | |||||
| Target Version | Fixed in Version | |||||
| Summary | 0001849: ClientCrash + "incorrect" errormessage | |||||
| Description | 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. | |||||
| Tags | No tags attached. | |||||
| Nightly Version | Automated (specify build number) | |||||
| Experimental Flags | UseNetworkMulti | |||||
| Option Flags | None | |||||
| Internal Build Number | ||||||
| Attached Files | ||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0000739) Terrikate (developer) 01-11-10 22:40 |
The third person throws anything to the ground? |
|
(0000740) wuffel (reporter) 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 (administrator) 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 (reporter) 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 (administrator) 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 (manager) 14-12-14 21:39 |
error message was fixed a while back. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 01-11-10 22:34 | wuffel | New Issue | |
| 01-11-10 22:40 | Terrikate | Note Added: 0000739 | |
| 01-11-10 23:26 | wuffel | Note Added: 0000740 | |
| 04-11-10 12:09 | MrSugarCube | Note Added: 0000743 | |
| 05-11-10 20:39 | wuffel | Note Added: 0000751 | |
| 14-11-10 19:54 | MrSugarCube | Category | executable - linux => executable - linux build |
| 03-12-10 02:05 | MrSugarCube | Note Added: 0000773 | |
| 14-12-14 21:39 | Ben | Note Added: 0002590 | |
| 14-12-14 21:39 | Ben | Status | new => closed |
| 14-12-14 21:39 | Ben | Assigned To | => Ben |
| 14-12-14 21:39 | Ben | Resolution | open => no change required |
|
Issue History |
| Copyright © 2000 - 2010 MantisBT Group |
 |