(Noticed while checking logs for bug 633725, but this assertion affects both FF and SM before/after.) Example: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1298747073.1298750402.4701.gz&fulltext=1 Rev3 Fedora 12 mozilla-central debug test mochitest-other on 2011/02/26 11:04:33 { 2194 INFO TEST-START | chrome://mochitests/content/a11y/accessible/events/test_docload.xul ... 2195 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/events/test_docload.xul | before wait for focus -- loaded: complete active window: ([object ChromeWindow @ 0x936eec0 (native @ 0x936d014)]) chrome://browser/content/browser.xul focused window: ([object Window @ 0xa1e04d0 (native @ 0xa85d7dc)]) chrome://mochitests/content/a11y/accessible/events/test_docload.xul desired window: ([object Window @ 0xa1e04d0 (native @ 0xa85d7dc)]) chrome://mochitests/content/a11y/accessible/events/test_docload.xul child window: ([object Window @ 0xa1e04d0 (native @ 0xa85d7dc)]) chrome://mochitests/content/a11y/accessible/events/test_docload.xul docshell visible: true 2196 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/events/test_docload.xul | already focused 2197 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/events/test_docload.xul | maybe run tests <load:true, focus:true> -- loaded: complete active window: ([object ChromeWindow @ 0x936eec0 (native @ 0x936d014)]) chrome://browser/content/browser.xul focused window: ([object Window @ 0xa1e04d0 (native @ 0xa85d7dc)]) chrome://mochitests/content/a11y/accessible/events/test_docload.xul desired window: ([object Window @ 0xa1e04d0 (native @ 0xa85d7dc)]) chrome://mochitests/content/a11y/accessible/events/test_docload.xul child window: ([object Window @ 0xa1e04d0 (native @ 0xa85d7dc)]) chrome://mochitests/content/a11y/accessible/events/test_docload.xul docshell visible: true ... ###!!! ASSERTION: Pending content insertions while initial accessible tree isn't created!: 'mContentInsertions.Length() == 0', file ../../../../accessible/src/base/NotificationController.cpp, line 225 NotificationController::WillRefresh [NotificationController.cpp:238] nsRefreshDriver::Notify [nsRefreshDriver.cpp:256] nsTimerImpl::Fire [nsTimerImpl.cpp:428] nsTimerEvent::Run [nsTimerImpl.cpp:519] nsThread::ProcessNextEvent [nsThread.cpp:633] NS_ProcessNextEvent_P [nsThreadUtils.cpp:250] mozilla::ipc::MessagePump::Run [MessagePump.cpp:110] MessageLoop::RunInternal [message_loop.cc:220] MessageLoop::RunHandler [message_loop.cc:203] MessageLoop::Run [message_loop.cc:176] nsBaseAppShell::Run [nsBaseAppShell.cpp:198] nsAppStartup::Run [nsAppStartup.cpp:220] XRE_main [nsAppRunner.cpp:3781] main [nsBrowserApp.cpp:158] libc.so.6 + 0x16bb6 } NB: I didn't check Windows. *** This assertion was added in bug 606924: http://mxr.mozilla.org/mozilla-central/source/accessible/src/base/NotificationController.cpp#225 196 NotificationController::WillRefresh(mozilla::TimeStamp aTime) 209 // Initial accessible tree construction. 210 if (mTreeConstructedState == eTreeConstructionPending) { 224 NS_ASSERTION(mContentInsertions.Length() == 0, 225 "Pending content insertions while initial accessible tree isn't created!");

Alexander, how does this happen?

Initial tree creation mutates frame tree, perhaps bug 630486.

AUTO-CLOSED. This bug untouched for over 2000 days. Please reopen if you can confirm the bug and help it progress.