Bug Tracker – Bug 1211

Crash while fast-forwarding during a demo netplay

Last modified: 2019-08-12 21:47:26 UTC
Bug 1211 - Crash while fast-forwarding during a demo netplay
Summary: Crash while fast-forwarding during a demo netplay
Status: NEW
Alias: None
Product: Odamex
Classification: Unclassified
Component: Client (show other bugs)
Version: 0.7.x (Old)
Hardware: All All
: P1 major
Assignee: Odamex Bug Reporter
URL:
Depends on:
Blocks:
 
Reported: 2016-11-20 15:16 UTC by Maëllig Desmottes
Modified: 2019-08-12 21:47 UTC (History)
3 users (show)

See Also:

Attachments
Demo (5.42 MB, application/octet-stream)
2016-11-20 15:16 UTC, Maëllig Desmottes 		Details
demo crash (311.53 KB, application/octet-stream)
2018-12-24 14:32 UTC, capodecima 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maëllig Desmottes 2016-11-20 15:16:40 UTC 
Created attachment 553 [details]
Demo

According to MSVC14's debugger, it seems this part of code is faulty: 

IN P_GetWeaponState :

"if (psp->state == NULL) return unknownstate;"

Demo provided as both attachment and GDrive : press DOWNARROW (to start o the match, then fast-forward 2/3 times). The game should immediately crash.

Demo: https://drive.google.com/open?id=0B8NOwl0yOYlrSS1pRnFLVHlLVzg

Odamex 0.7.0 GIT used (rev: https://github.com/odamex/odamex/commit/9ebf8e115d587565ae9d7853054f16edaf51ecb8 )
Comment 1 HeX_Vulture 2018-10-14 19:56:58 UTC 
The demo does not crash for me in Windows 10 SDL2 64-bit. However, there are issues fast forwarding including the game missing textures and being unable to use the console until the player dies and respawns. Upon respawn the game fixes itself and console functions are available again. After the game fixes itself it appears the only noticable bug is that player names are missing int he scoreboard.

Revision used to test: 598ca65
Comment 2 capodecima 2018-12-24 14:32:06 UTC 
Created attachment 561 [details]
demo crash
Comment 3 HeX_Vulture 2019-08-12 21:47:26 UTC 
The bug I was experiencing was bug 1244