MantisBT - Zandronum |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0002177 | Zandronum | [All Projects] Bug | public | 2015-04-06 13:49 | 2015-04-13 20:19 |
|
| Reporter | John Zombie | |
| Assigned To | | |
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | no change required | |
| Platform | PC x64 | OS | Windows | OS Version | 7 SP1 |
| Product Version | 2.0 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0002177: Zandronum randomly closes itself |
| Description | In the middle of the game Zandronum just freezes for 1-2 seconds, then crashes/closes itself without any message/crash report whatsoever(as if i ALT-F4'd).
If I try to rejoin the same server immediately after the crash occurred it says
"client_checkformissingpackets: missing more than 1024 packets. Unable to recover." (http://i.imgur.com/8EMKL3S.png)
If i wait a few seconds more it lets me rejoin, just to see the same bug occurring again sooner or later. |
| Steps To Reproduce | No idea how to exactly reproduce this since no demo gets saved after it crashes, it always happens when playing in CTF servers(just spectating in there doesn't seem to trigger it though), while it never happened on duel servers(yet).
Haven't played other gamemodes since 2.0's release so I can't speak about those |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2015-04-06 13:49 | John Zombie | New Issue | |
| 2015-04-08 14:13 | John Zombie | Note Added: 0012073 | |
| 2015-04-08 14:14 | John Zombie | Note Edited: 0012073 | bug_revision_view_page.php?bugnote_id=12073#r6934 |
| 2015-04-08 14:15 | John Zombie | Note Edited: 0012073 | bug_revision_view_page.php?bugnote_id=12073#r6935 |
| 2015-04-08 14:28 | Dusk | Note Added: 0012074 | |
| 2015-04-08 19:39 | Arco | Priority | immediate => normal |
| 2015-04-13 19:16 | John Zombie | Note Added: 0012097 | |
| 2015-04-13 20:19 | Watermelon | Note Added: 0012100 | |
| 2015-04-13 20:19 | Watermelon | Status | new => closed |
| 2015-04-13 20:19 | Watermelon | Resolution | open => no change required |
|
Notes |
|
|
(0012073)
|
|
John Zombie
|
2015-04-08 14:13
(edited on: 2015-04-08 14:15) |
|
Update: the crash reporting feature itself is definitely broken. Did a few tests using the crashout console command, and a report gets generated only immediately after the exe gets launched, but if I either launch a new game / wait a few more seconds on the main menu and then call crashout, it just hangs 1-2 seconds and closes itself without generating any report whatsoever(pretty much the same issue i get on ctf servers).
|
|
|
|
(0012074)
|
|
Dusk
|
|
2015-04-08 14:28
|
|
|
Could be a duplicate of 0002145 then. |
|
|
|
|
ok so:
-zandronum closing itself when crashing instead of generating a report was apparently caused by some Raptr application that came bundled when updating AMD video drivers, closing said app made zandronum generate reports again
-I've been testing the custom build Water made for 0002145 and the problem seems fixed, so I guess this bug can be considered resolved |
|
|
|
|
|