Bad object placement leads to * stack smashing detected *: terminated
New, NormalPublic
Actions

Description

Running 1.27 server under Debian bookworm and loading some object spawner loader json I found on the internet resulted after some minutes! in one of the infamous *stack smashing detected* crashes.

Investigating the file showed one object being placed outside of the world.
As this is something that could easily happen and there is no sane way to find the bug except for spending some hours with git-bisect, I think you should ensure that when placing objects in the world they are placed in a sane location and instead of crashing filter them out and create an appropriate error message.

Details

Severity: Minor
Resolution: Open
Reproducibility: Always
Operating System: Linux x64
Operating System Version: Debian Bookworm
Category: Server

Steps To Reproduce

Load this json:

{
    "Objects": [
         {
            "name": "Land_Roadblock_Table",
            "pos": [
                9002.890625,
                733.824951,
                5196127.5
            ],
            "ypr": [
                90,
                0,
                0
            ],
            "scale": 1,
            "enableCEPersistency": false
        }
    ]
}

start the server and wait, for me the stack smashing error usually appeared after 1-5 minutes.

Event Timeline

bzed created this task.Wed, Feb 26, 5:51 PM

Bad object placement leads to *** stack smashing detected ***: terminatedNew, NormalPublicActions

Description

Details

Event Timeline

Bad object placement leads to * stack smashing detected *: terminated
New, NormalPublic
Actions