Dedicated server crashes when calling addCuratorEditableObjects [allUnits, true]; when some units in allUnits may be null objects or objects whos locality system is not valid.
{F25338} {F25339}Description
Description
Details
Details
- Legacy ID
- 2224268404
- Severity
- None
- Resolution
- Open
- Reproducibility
- Always
- Category
- Dedicated Server
Steps To Reproduce
- Have 3 users in a dedicated server in a mission
- Have 1 user disconnect during briefing, prior to mission start
- call addCuratorEditableObjects [allUnits, true];
Server crashes.
Additional Information
Crash dump attached.
Event Timeline
Comment Actions
Hello,
I was trying but could not reproduce the problem. Is it possible to upload a simple mission?
Thank you very much.
Comment Actions
I've narrowed this down to executing addCuratorEditableObjects when an object is null but not completely deleted yet. This happens when players become out of sync and a null object persists on a client which does not exist on the server.
I cannot reliable reproduce this, but it does reproduce sometimes with the attached mission.
Comment Actions
Further testing: It is definitely when an invalid object exists that this will cause a crash. Basic testing is to play a large MP game until you are receiving "Object not found" errors, then run the command on that object. It will crash.
Assuming a null dereference in addCuratorEditableObjects on an invalid object.
Comment Actions
That issue recently came up on official zeus servers. It was fixed within 2 days of being reported to me. I don't know what went wrong here 5 years ago, but something certainly did.