In the testcase in https://codereview.chromium.org/2099523002,
at the time of detaching the subtree (including the floating element),
the floating element attempts to remove itself from the floating element
set of its container, but (a) it appears to be in multiple floating
elements sets, and (b) there is at least one that it's in that it doesn't
get removed from.
A subsequent call to unsafeClone when moving anonymous children
ends up passing around an already-deleted LayoutObject pointer.
The root cause seems to be incorrect code for floats.
Comment 1 by e...@chromium.org
, Jun 28 2016Status: Assigned (was: Untriaged)