0002075: Program crash when activating Polyobj_DoorSwing

Notes
(0011481) Torr Samaho (administrator) 2015-01-21 18:54	Thanks! I can reproduce the crash in Zandronum 2.0 and also in GZDoom revision 900. It's fixed in recent GZDoom versions though. Can somebody check when (G)ZDoom fixed this?

(0011487) WaTaKiD (updater) 2015-01-21 20:21	if it helps, the crash stops with gzdoom 1.6.0-r1418, tho when 'using' the polyobject, it seems to work fine but displays an error message: "Invalid mirror polyobj num -45 for polyobj num 1" i dont know anything about polyobjects so idk if this is mapper error or wut, but the message goes away with 1.8.2 for zdoom: 2.6.0: no crash, 2.7.1: no message

(0011491) Inkubus (reporter) 2015-01-21 20:58	Thanks, I noticed the message as well when playing on zdoom.

(0011515) Edward-san (developer) 2015-01-23 11:44 edited on: 2015-01-23 15:22	It's fixed in r3288. Applied the patch (only po_man.cpp) to 2.0, works like a charm offline. When static code analysis (done by me) helps finding issues ... Meanwhile, with the fix, online, there's an inconsistency, which happens when a client blocks a polyobject: offline, the polyobject is blocked until the player moves away, but online, the client sees the polyobject rotate continuously, even if it should not, until the client moves away, then the polyobject works fine. [edit] Just mentioning that this commit is the same as the one reported in 0001910 , with the changes in p_setup.cpp. [edit] Ok, I'll move discussion of the problems with the fixed program on another ticket, in order to keep it clean from the original purpose of this ticket, ie just fix the crash.

(0011526) Torr Samaho (administrator) 2015-01-25 10:16	I backported the fix.

(0011545) WaTaKiD (updater) 2015-01-25 19:52	after testing with 2.0-r150125-1008, crash seems fixed (that message is gone too)

**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 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-01-21 18:50	Inkubus	New Issue
2015-01-21 18:50	Inkubus	File Added: Polyobj Crash.wad
2015-01-21 18:54	Torr Samaho	Note Added: 0011481
2015-01-21 20:21	WaTaKiD	Note Added: 0011487
2015-01-21 20:58	Inkubus	Note Added: 0011491
2015-01-23 11:44	Edward-san	Note Added: 0011515
2015-01-23 11:45	Edward-san	Note Edited: 0011515	View Revisions
2015-01-23 11:47	Edward-san	Note Edited: 0011515	View Revisions
2015-01-23 11:47	Edward-san	Assigned To	=> Torr Samaho
2015-01-23 11:47	Edward-san	Status	new => assigned
2015-01-23 11:51	Edward-san	Note Edited: 0011515	View Revisions
2015-01-23 13:20	Edward-san	Note Edited: 0011515	View Revisions
2015-01-23 15:20	Edward-san	Note Edited: 0011515	View Revisions
2015-01-23 15:22	Edward-san	Note Edited: 0011515	View Revisions
2015-01-25 10:16	Torr Samaho	Note Added: 0011526
2015-01-25 10:16	Torr Samaho	Status	assigned => needs testing
2015-01-25 19:52	WaTaKiD	Note Added: 0011545
2015-01-25 21:24	Dusk	Status	needs testing => resolved
2015-01-25 21:24	Dusk	Fixed in Version	=> 2.0
2015-01-25 21:24	Dusk	Resolution	open => fixed
2018-09-30 23:04	Blzut3	Status	resolved => closed

Relationships