Crash on RendererUpdateManager::RemoveRenderer when undoing painting tiles to the scene

Within the project a custom script is adding new additional objects to the Tilemap which are not registered with the undo system. Any change to the Tilemap such as child objects created with Instantiate, added via SetParent, destroyed via DestroyImmediate etc should be registered with the Undo System using their undoable counterpart https://docs.unity3d.com/ScriptReference/Undo.html.

Within the project a custom script is adding new additional objects to the Tilemap which are not registered with the undo system. Any change to the Tilemap such as child objects created with Instantiate, added via SetParent, destroyed via DestroyImmediate etc should be registered with the Undo System using their undoable counterpart https://docs.unity3d.com/ScriptReference/Undo.html. This fix catches the child objects left dangling and warns the user therefore avoiding the crash. To make the action fully undoable some updates will be required to user script.

Within the project a custom script is adding new additional objects to the Tilemap which are not registered with the undo system. Extensions to the Tilemap system outside the Tilemap editing ecosystem such as those in the example project should implement editor Undo themselves in their system. Any change to the Tilemap such as child objects created with Instantiate, added via SetParent, destroyed via DestroyImmediate etc should be registered with the Undo System using their undoable counterpart https://docs.unity3d.com/ScriptReference/Undo.html.