Another possibility I meet still inline with what @Alex said, is that I had to
monkey patch the PopupManagerImpl for an application I migrated from Flex 3 and
had to revamp MarshalPopUpData / PopUpManagerMarshalMixin (that wasn't
necessary in Flex 3 though) and therefore had to add MarshallingSupport in FM
has I shown before.
But doesn't seem the case here and the clue is trying to find what drags those
classes, I'm thinking much more as @Alex mentioned, about a third-party lib
that make use of it.
@Chris AFAIK, There is nothing specific to do in FM except including this
support at user configuration level.
By curiosity, is there anything special that could cause that in:
com.ilias.solutions.flexappeal.status::StatusManager/showStatus()[/etc/ilias/releasemgt/work/Framework/branch-SDK4.6/ilias/i3g/flex/framework/FlexAppealFramework/FlexAppealFrameworkSharedLib/src/main/flex/com/ilias/solutions/flexappeal/status/StatusManager.as:359]
Frédéric THOMAS
----------------------------------------
> From: aha...@adobe.com
> To: users@flex.apache.org
> Subject: Re: AW: issue with Popupmanager SDK 4.14 / Flexmojos 7.1
> Date: Wed, 17 Jun 2015 05:14:14 +0000
>
>
>
> On 6/16/15, 1:35 AM, "L'Hommelet Filip"
> <Filip.L'homme...@ilias-solutions.com> wrote:
>
>>Well,
>>You wouldn't believe it... but that did the trick!
>
> Well, I do believe it, but now all of your code is doing extra
> MarshallingSupport work. This should not be necessary unless you are
> loading SWFs across SecurityDomains or SWFs compiled with different
> versions. If you start to notice performance issues, that could be the
> reason, although generally the overhead is not noticed.
>
> The root cause still seems like some SWF is loading the
> PopUpManagerMarshalMixin. Normally, including MarshallingSupport drags in
> PopUpManagerMarshalMixin and other related classes. But if you link in
> just PopUpManagerMarshalMixin without linking in MarshallingSupport, I
> would expect the symptoms you are seeing.
>
> -Alex
>
