This is in Flex 3.2:
We have a rare crash in one of our components. We have no repro case,
but we were able to catch it in the debugger once and get a callstack.
Ive included the callstack at the bottom of this message. The error is:
-": TypeError: Error #1034: Type Coercion failed: cannot convert
mx.controls::flexnativem...@234d7df1 to flash.display.DisplayObject"
called from:
"mx.managers.layoutClasses::PriorityQueue/removeLargestChild"
Trying to figure out how this could happen... No component on this page
actually even uses FlexNativeMenu... So that's odd. But we do use it in
other parts of our application. We use it declared in mxml and we use it
declared in .as. But, we don't do anything strange with it, and
certainly not on this page.
Tried to do research on exactly what removeLargestChild does, and why
it would be trying to remove a FlexNativeMenu, but no dice.
Anyone have any clues as to what I should dig in for here, or what the
LayoutManager may be trying to do here?
-ctm
callstack:
Main Thread (Suspended: TypeError: Error #1034: Type Coercion failed:
cannot convert mx.controls::flexnativem...@234d7df1 to
flash.display.DisplayObject.)
mx.managers.layoutClasses::PriorityQueue/removeLargestChild
mx.managers::LayoutManager/validateClient
mx.core::UIComponent/validateNow
mx.core::Container/createOrDestroyScrollbars
mx.core::Container/createScrollbarsIfNeeded
mx.core::Container/createContentPaneAndScrollbarsIfNeeded
mx.core::Container/validateDisplayList
mx.managers::LayoutManager/validateDisplayList
mx.managers::LayoutManager/doPhasedInstantiation
Function/http://adobe.com/AS3/2006/builtin::apply [no source]
mx.core::UIComponent/callLaterDispatcher2
mx.core::UIComponent/callLaterDispatcher
