It seems like FloatingWindow is being added to the queue with QueueObjectLayout in FloatingWindow.cpp, but might not be removed from the queue before it's deleted. Its ancestor Area has the same potential issue, as well. So, moving the RemoveObjectFromLayoutQueue call in View and Layout destructors to their common ancestor Area's destructor (as in the attached patch) should fix that issue (and this bug, unless something else is overwriting the objects in that queue).
It seems like FloatingWindow is being added to the queue with QueueObjectLayout in FloatingWindow.cpp, but might not be removed from the queue before it's deleted. Its ancestor Area has the same potential issue, as well. So, moving the RemoveObjectFro mLayoutQueue call in View and Layout destructors to their common ancestor Area's destructor (as in the attached patch) should fix that issue (and this bug, unless something else is overwriting the objects in that queue).