There appears to be a failry serious bug that I think was introduced
in the history manager in the latest release 2.0.1
I never got this errro until I updated and I now see it in a variety
of situations (including whenever I run testcases. )
Shutting down the borwoser or even switching borwsers does NOT help. I
mostly see it when I am running from the flex builder, but when you
are trying to run tests -- this becomes failry serious and very time
consuming.
The error message is:
ArgumentError: Error #2082: Connect failed because the object is
already connected.
at flash.net::LocalConnection/connect()
at mx.managers::HistoryManagerImpl$iinit()
at mx.managers::HistoryManagerImpl$/getInstance()
at mx.core::Singleton$/getInstance()
at mx.managers::HistoryManager$/get ::impl()
at mx.managers::HistoryManager$/register()
at mx.containers::ViewStack/::addedHandler()
at flash.display::DisplayObjectContainer/addChildAt()
at
mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::$addChildAt()
at mx.core::Container/addChildAt()
at mx.core::Container/addChild()
at mx.core::Container/createComponentFromDescriptor()
at mx.core::Container/createComponentsFromDescriptors()
at mx.core::Container/mx.core:Container::createChildren()
at mx.core::UIComponent/initialize()
at mx.core::Container/initialize()
at
mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at
mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at mx.core::Container/addChildAt()
at mx.core::Container/addChild()
at mx.core::Container/createComponentFromDescriptor()
at mx.core::Container/createComponentsFromDescriptors()
at mx.containers::Panel/createComponentsFromDescriptors()
at mx.core::Container/mx.core:Container::createChildren()
at mx.containers::Panel/mx.containers:Panel::createChildren()
at mx.core::UIComponent/initialize()
at mx.core::Container/initialize()
at
mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at
mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at mx.core::Container/addChildAt()
at mx.core::Container/addChild()
at mx.core::Container/createComponentFromDescriptor()
at mx.core::Container/createComponentsFromDescriptors()
at mx.core::Container/mx.core:Container::createChildren()
at mx.core::UIComponent/initialize()
at mx.core::Container/initialize()
at
mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at
mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at mx.core::Container/addChildAt()
at mx.core::Container/addChild()
at mx.core::Container/createComponentFromDescriptor()
at mx.core::Container/createComponentsFromDescriptors()
at mx.core::Container/mx.core:Container::createChildren()
at mx.core::UIComponent/initialize()
at mx.core::Container/initialize()
at flexunit.flexui::TestRunnerBase/initialize()
at
mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at
mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at mx.core::Container/addChildAt()
at mx.core::Container/addChild()
at mx.core::Container/createComponentFromDescriptor()
at mx.core::Container/createComponentsFromDescriptors()
at mx.core::Container/mx.core:Container::createChildren()
at mx.core::UIComponent/initialize()
at mx.core::Container/initialize()
at mx.core::Application/initialize()
at sgtTestRunner/initialize()
at
mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::childAdded()
at mx.managers::SystemManager/::initializeTopLevelWindow()
at mx.managers::SystemManager/::docFrameHandler()
Is Adobe planning on addressing this issue? I know other coders are
posting on this. I have heard nothing from Abode however.
Chris Warden
