Destroyed components can still have a redraw queued in some scenarios

[headjoe3]

This line of code moves queued redraws to the next frame if called in the middle of a redraw:

This can cause issues by re-queueing redraws for destroyed components. In a light version of Rocrastinate, I implemented a fix by tracking a "destroyed' property of components.