0001252: Zero length Looping state crashes in multiplayer

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

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001252

Zandronum

[All Projects] Bug

public

2013-01-16 17:09

2013-01-16 17:56

Reporter

HexaDoken

Assigned To

Priority

high

Severity

block

Reproducibility

always

Status

closed

Resolution

duplicate

Platform

Microsoft

Windows

OS Version

XP/Vista/7

Product Version

1.0

Target Version

Fixed in Version

Summary

0001252: Zero length Looping state crashes in multiplayer

Description

Missile:
TROO A 0 A_Jump(256,"Missile1","Missile2")
Loop

This code. What we have here is a zero-length state that loops itself. Normally, it should result in an infinite loop, but we have A_Jump(256) there, which jumps out of the state with 100% chance before the looping is met.

The problem about it? Offline, it works perfectly fine. Online, as soon as the state is entered by an actor, all clients freeze instantly. Attempting to reconnect to the server results in being instantly kicked due to too much missed packets.

On a modder's side, this code can be easily fixed by replacing Loop with Goto Statename. Despite having the exact same functionality, doing so will avoid online freezes. However, I'm tired of fixing this bug for other modders. If you could make zandronum not freeze this bad because of this code, I'd be really grateful.

Example wad below!

Steps To Reproduce

Host a server with an example wad below. The wad replaces standart doom imps with a modified version, that randomly shoot you with imp fireballs or caco fireballs. As soon as an imp decides to shoot you online, all clients freeze solid.

Attached Files

crashexample.wad [^] (349 bytes) 2013-01-16 17:09

Relationships

duplicate of

0001200

closed

Torr Samaho

"randomguy" causes clients to freeze in online games

Notes
There are no notes attached to this issue.

**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
2013-01-16 17:09	HexaDoken	New Issue
2013-01-16 17:09	HexaDoken	File Added: crashexample.wad
2013-01-16 17:56	Dusk	Relationship added	duplicate of 0001200
2013-01-16 17:56	Dusk	Status	new => closed
2013-01-16 17:56	Dusk	Resolution	open => duplicate

Questions or other issues? Contact Us.

Links

Doom and Doom II are the property of id Software.