81525 2012-03-19 10:35:54 -0700 ASSERTION FAILURE: !oldLast->m_nextSibling in WebFrameProxy::appendChild causing "crashes" on Lion Intel Debug WebKit2 testers 2012-03-19 17:00:29 -0700 1 1 1 Unclassified WebKit Frames 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 81453 http://build.webkit.org/results/Lion%20Intel%20Debug%20(WebKit2%20Tests)/r111185%20(5032)/fast/frames/iframe-reparenting-unique-name-crash-log.txt InRadar, LayoutTestFailure, MakingBotsRed, Regression P2 Normal --- 1 jberlin webkit-unassigned andersca ap jberlin sam webkit-bug-importer oldest_to_newest 581924 0 jberlin 2012-03-19 10:35:54 -0700 void WebFrameProxy::appendChild(WebFrameProxy* child) { ASSERT(child->page() == page()); ASSERT(!child->m_parentFrame); ASSERT(!child->m_nextSibling); ASSERT(!child->m_previousSibling); child->m_parentFrame = this; WebFrameProxy* oldLast = m_lastChild; m_lastChild = child; if (oldLast) { ASSERT(!oldLast->m_nextSibling); child->m_previousSibling = oldLast; oldLast->m_nextSibling = child; } else m_firstChild = child; } http://build.webkit.org/results/Lion%20Intel%20Debug%20(WebKit2%20Tests)/r111185%20(5032)/fast/frames/iframe-reparenting-unique-name-crash-log.txt I have to run all fast/frames tests under WKTR to reproduce this locally on my Lion machine - running just fast/frames/iframe-reparenting-unique-name.html is not enough. However, it always seems to "crash" in that test. 581925 1 webkit-bug-importer 2012-03-19 10:36:29 -0700 <rdar://problem/11074068> 581929 2 jberlin 2012-03-19 10:42:05 -0700 Correction: I can reproduce this locally by just running the fast/frames/iframe-reparenting* tests. 582475 3 ap 2012-03-19 17:00:29 -0700 Same thing as bug 81453. *** This bug has been marked as a duplicate of bug 81453 ***