Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002145Zandronum[All Projects] Bugpublic2015-03-30 09:402018-09-30 21:38
ReporterWaTaKiD 
Assigned ToDusk 
PrioritynormalSeveritycrashReproducibilityrandom
StatusclosedResolutionfixed 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version2.0 
Target Version2.1Fixed in Version2.1 
Summary0002145: random crash upon respawning in ctf
Descriptionedd's crashed a couple times in 2.0 ctf which hes never experienced before in 1.3
demo:'http://speedy.sh/7svwk/2015.03.29-20.02.54-idl2014a.map15patch.odaflagxpk3.zandrospree2rc2pk3.cld [^]'
Steps To Reproducedie in ctf
respawn
hope it crashes

for the demo:
skip to map27
crash happens at roughly 7 mins in
Additional Information> zandronum.exe!AWeapon::Use(bool pickup=false) Line 118 + 0x19 bytes C++
     zandronum.exe!CLIENT_EndTick() Line 720 C++
     zandronum.exe!TryRunTics() Line 1866 C++
     zandronum.exe!D_DoomLoop() Line 1228 C++
Attached Fileszip file icon CrashReport.zip [^] (33,940 bytes) 2015-03-30 09:40

- Relationships

-  Notes
User avatar (0011934)
Dusk (developer)
2015-03-30 13:33

I can't get this to happen no matter what but I did notice that the way weapons are used to trigger a switch was inadvertently changed when the nametags were fixed, and it's in this new function where it appears to crash. Whoops.

I'll correct the way weapons are used and hope it works.
User avatar (0011936)
Dusk (developer)
2015-03-30 13:44

Hopefully fixed now
User avatar (0011943)
cobalt (updater)
2015-03-30 18:00

Issue addressed by commit f16f4a3f47cd: - fixed the way weapons should be switched to on the client (hopefully fixes 2145)
Committed by Teemu Piippo [Dusk] on Monday 30 March 2015 16:43:47

Changes in files:
 docs/zandronum-history.txt | 1 +
 src/cl_main.cpp | 2 +-
 2 files changed, 2 insertions(+), 1 deletions(-)
User avatar (0012095)
Watermelon (developer)
2015-04-13 17:21

I made a binary for people to test this with the fix above, and so far everyone has said that it has completely resolved the issue. They've been able to play for hours with no crash (whereas it usually tanked within 5 minutes). Therefore this looks resolved at this point.

Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2015-03-30 09:40 WaTaKiD New Issue
2015-03-30 09:40 WaTaKiD File Added: CrashReport.zip
2015-03-30 13:32 Dusk Assigned To => Dusk
2015-03-30 13:32 Dusk Status new => assigned
2015-03-30 13:33 Dusk Note Added: 0011934
2015-03-30 13:44 Dusk Note Added: 0011936
2015-03-30 13:44 Dusk Status assigned => needs review
2015-03-30 13:45 Dusk Severity minor => crash
2015-03-30 13:45 Dusk Target Version => 2.1
2015-03-30 18:00 cobalt Status needs review => needs testing
2015-03-30 18:00 cobalt Description Updated View Revisions
2015-03-30 18:00 cobalt Steps to Reproduce Updated View Revisions
2015-03-30 18:00 cobalt Additional Information Updated View Revisions
2015-03-30 18:00 cobalt Note Added: 0011943
2015-04-13 17:21 Watermelon Note Added: 0012095
2015-04-13 17:21 Watermelon Status needs testing => resolved
2015-04-13 17:21 Watermelon Fixed in Version => 2.1
2015-04-13 17:21 Watermelon Resolution open => fixed
2018-09-30 21:38 Blzut3 Status resolved => closed






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker