MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002624Zandronum[All Projects] Bugpublic2016-02-08 06:382018-09-30 21:59
ReporterWaTaKiD 
Assigned ToTorr Samaho 
PrioritynormalSeverityminorReproducibilityrandom
StatusclosedResolutionfixed 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version3.0-beta 
Target Version3.0Fixed in Version3.0 
Summary0002624: randomly crashed after getting kicked for missing packets
Descriptionwhile playing map31 of btsx e2, after about half an hour in i was dead with 1 life remaining, spectating another player and i started to lag, got kicked for missing packets, and upon exiting zandro i was met with a crash box

unfortunately this seems like one of those random crashes that happen outta the blue so im not sure how easy itd be to reproduce it, and the wads used require zan 3.0 so idk if its possible in zan 2.1.2, but im making this ticket just in case

crash report attached, build used is 3.0-r160131-2023
Steps To Reproduce
Additional Informationwads used:

'http://www.best-ever.org/download?file=rfnailgn-wws2.wad [^]'
'http://www.best-ever.org/download?file=btsx_e2a.wad [^]'
'http://www.best-ever.org/download?file=btsx_e2b.wad [^]'
'http://www.best-ever.org/download?file=rfnailgn-nofriendlyfirepuff.wad [^]'
'http://www.best-ever.org/download?file=newtextcolours_260.pk3 [^]'

also heres the backtrace:

> zandronum.exe!CommandDrawNumber::Tick(const SBarInfoMainBlock * block, const DSBarInfo * statusBar, bool hudChanged) Line 1297 C++
     zandronum.exe!SBarInfoCommandFlowControl::Tick(const SBarInfoMainBlock * block, const DSBarInfo * statusBar, bool hudChanged) Line 274 C++
     zandronum.exe!DSBarInfo::Tick() Line 1158 C++
     zandronum.exe!P_Ticker() Line 356 C++
     zandronum.exe!G_Ticker() Line 1688 C++
     zandronum.exe!TryRunTics() Line 1904 C++
     zandronum.exe!D_DoomLoop() Line 1320 C++
     zandronum.exe!D_DoomMain() Line 3251 C++
TagsNo tags attached.
Relationships
Attached Fileszip CrashReport.zip (26,595) 2016-02-08 06:38
/tracker/file_download.php?file_id=1733&type=bug
Issue History
Date ModifiedUsernameFieldChange
2016-02-08 06:38WaTaKiDNew Issue
2016-02-08 06:38WaTaKiDFile Added: CrashReport.zip
2016-03-07 01:28WaTaKiDAdditional Information Updatedbug_revision_view_page.php?rev_id=8825#r8825
2016-03-07 01:31WaTaKiDNote Added: 0014564
2016-03-20 14:04Torr SamahoNote Added: 0014586
2016-03-20 16:14cobaltAssigned To => Torr Samaho
2016-03-20 16:14cobaltStatusnew => needs testing
2016-03-20 16:14cobaltTarget Version => 3.0
2016-03-20 16:14cobaltDescription Updatedbug_revision_view_page.php?rev_id=8835#r8835
2016-03-20 16:14cobaltAdditional Information Updatedbug_revision_view_page.php?rev_id=8836#r8836
2016-03-20 16:14cobaltNote Added: 0014596
2016-10-09 22:35Ru5tK1ngNote Added: 0015869
2016-10-09 22:35Ru5tK1ngFixed in Version => 3.0
2016-10-09 22:35Ru5tK1ngDescription Updatedbug_revision_view_page.php?rev_id=9650#r9650
2016-10-09 22:35Ru5tK1ngAdditional Information Updatedbug_revision_view_page.php?rev_id=9651#r9651
2016-10-09 22:36Ru5tK1ngStatusneeds testing => resolved
2016-10-09 22:36Ru5tK1ngResolutionopen => fixed
2018-09-30 21:59Blzut3Statusresolved => closed

Notes
(0014564)
WaTaKiD   
2016-03-07 01:31   
edited the wad links as the previous ones were dead

also, during today's'http://zandronum.com/forum/showthread.php?tid=7096 [^]' several people crashed after being kicked for packets, and all 8 or so crash reports gave the same thing as stated in this ticket's additional information
(0014586)
Torr Samaho   
2016-03-20 14:04   
The crash log pointed to a problem with SBARINFO. It's hopefully fixed now.
(0014596)
cobalt   
2016-03-20 16:14   
Issue addressed by commit 1b18f00b1eca: Fixed potential client crashes with SBARINFO (addresses 2624).
Committed by Benjamin Berkels [Torr Samaho] on Wednesday 31 December 1969 23:59:57

Changes in files:

 src/g_shared/sbarinfo_commands.cpp | 8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
(0015869)
Ru5tK1ng   
2016-10-09 22:35   
Since there haven't been any issues, that seems to have fixed the issue.