Doh that was supposed to be a reply to Paul.
It's a module called "Launcher of Target platform type "Desktop" and output
type of "Application" (shows as "Flex application for desktop (Adobe AIR)"
from the "General" section of the module.
Then you need to configure the "Air Package" section to
Unfortunately I can't share the project but I can share with you the basics.
There was a thread from a while back when we were working through some of
the problems:
http://apache-flex-users.246.n4.nabble.com/SWFLoader-not-pulling-through-all-sub-SWF-styles-td17851.html
The crux of the
You're not wrong! There are other bits and pieces we are working through that
are not working as expected.
If I get some time I'll try and get an example app together to pass on the
knowledge.
Our current problem is we use the "IBM ILOG Elixir" component (now owned by
RogueWave but we still use
I think we may have our wires crossed in terms of what we are trying to
achieve here.
The Air App is simply a surrogate browser, simply a means to load our
existing application SWF. There doesn't need to be any communication between
Air App and SWF other than it has a place to host/show it. So
We are using Flex SDK 4.6.0.23201 (with built in AIR SDK 3.1.0.4880) for both
the Air application host and the SWF being loaded.
We gave up on the styling problem (loading the SWF in to the same
application domain).
We swapped it to load in to it's own application domain, ala:
*var
Not sure if this forum is still as active as it once was but I'll give it a
go...
We have a massive Flex application that we are probably not going to have
converted to HTML/JS by the time FlashPlayer is turned off at the end of
2020.
So as a stop gap solution we are going to try the locally
Alex Harui-2 wrote
> If you haven't tried an older browser, I would recommend doing
> so.reserved=0
Stuck on V47 of Firefox with the NPAPI debugger and it now connects and runs
the Profiler :)
Didn't realise the mm.cfg got written to dynamically We saw that in
motion...
--
Sent from:
That's promising, what do you have in your mm.cfg file?
Alex Harui-2 wrote
> Today I installed FB 4.7 on my personal Windows 10 computer. I have the
> debugger version of FP32 in an older FIreFox (v47). The profiler worked
> for me.
>
> HTH,
> -Alex
--
Sent from:
We have a very large enterprise application with a small/medium memory leak.
The last time we really profiled the app was when we, as developers, still
all used Windows 7 and it all world swimmingly.
At that time we used a combination of the Flash Builder Profiler and Adobe
Scout. Both gave
SOLVED! (It's a bug in IE 11, but there is a workaround)
So for prosperity I thought I'd share where this ended up.
After much faffing, I managed to get into contact with an Adobe
representative and we started technical liaison. After many emails,
performance logs and videos we got to the bottom
Alex Harui wrote
> It doesn't take a lot of AS to make the player spend a lot of time on the
> rendering. You just have to make a few lineTo calls with the right
> line-joins.
>
> Did we eliminate GPU vs non-GPU rendering?
Ok, was diverted on to some other stuff but this is still a major issue.
clintm wrote
> It might be memory related. How much memory is it using?
>
> If it is memory related it might be IE's Enhanced Protection Mode (or lack
> there of).
Hiya clintm, thanks for responding.
We've had our fair share of memory related problems with the GCOD rearing
its ugly head every
Alex Harui wrote
> Yes, if you single step for a while and end up back at debugTickler, then
> you saw all of the AS3 running in the frame, and it looks like there isn't
> any serious work for it to do.
>
> Of course, if you can also get a debugger on the SWF when it isn't having
> the
I think the staticRenderHandler is a red herring, FTETextField sets event
listeners up to call that method on every RENDER and ENTER_FRAME so we'd
expect that to be called all the time.
Here are some screenshots that may provide some more insight and make things
a bit clearer from what I'm seeing
Tom Chiverton wrote
> Graphics drivers ? Maybe acceleration is disabled ?
I did wonder about graphic drivers. All the machines I've seen this happen
on are touch screens. However, the client's machine are not touch screen.
Hardware acceleration is on for the machines I've played around with.
Alex Harui wrote
> "Other" includes "Other (activities such as garbage collection, event
> processing, and so on)"
It's not GC (that has it's own activity which can be seen) it's the sub
section activity "Runtime Overhead"
Alex Harui wrote
> If you have a debugger on it, I would just wait until
An interesting read and I have encountered this type of problem before.
However, in all the cases I have experienced this it always behaves the
same, it's never been machine specific.
The problem only occurs on some machines, connecting to exactly the same
appserver, serving up exactly the same
Hiya,
We have a very large enterprise Flex/Flash application which makes extensive
use of IBM's ILOG Elixir Gantt component.
Since Windows 10 we have, internally, experienced lag when interacting with
the gantt charts so bad it made the application unusable. This was using
IE11 and experienced
I would love to know this too.
FB profiler falls over constantly with big apps and is sloo! Plus it
lies about GC root things. Scout is great for performance analysis but awful
for memory leak diagnostics.
Mark Line wrote
> Hi,
>
> Has anyone managed to get the following plugin to
I already have the line -compiler.theme=${flexlib}\themes\Halo\halo.swc.
IntelliJ is slightly different with no theme selector so you have to
manually specify that.
If I don't specify that it defaults to the spark theme and I get 110 of
these type warnings instead:
Warning:[ProductClient]:
Is it possible to remove the following Flex 4.6 SDK warnings?
Warning:[ProductClient]:
C:\Workspaces\sdks\Flex\4.6.0\frameworks\libs\spark.swc$defaults.css: The
style 'backgroundColor' is only supported by type
'spark.components.BorderContainer' with the theme(s) 'spark, mobile'.
We use Spark components and MX components.
But.this is moaning about the Spark.swc defaults.css within the SDK
itself. How do I supply a custom default.css to that?
Alex Harui wrote
Well, it sounds like you are using Spark classes, and I don’t think Halo
has a skin for all of those Spark
One of the devs involved in this has never installed the trial so we are
going to use his machine while waiting for the licenses.
When he's not around I think I will shove it on a VM as you suggest.
Licenses are going through the internal wheel at the moment.
Wonder if it's worth contacting
I am back in the world of profiling (unhappy face!)...
My FlashBuilder Trial has expired and I need to go through our long winded
internal IT infrastructure to get a couple of licenses sorted.
Is there any way to increase the trial period or get it reset while that is
all happening?
--
View
I have been using Adobe Scout but it's not as helpful in locating what is
pinning things.
You've helped me in the past with memory leaks :)
Going for the uninstall / reinstall to see if that will let me proceed for
the time being.
Alex Harui wrote
I don’t know of any way to do that. Have you
So for prosperity and incase anyone else needs this information.
After a bit of VM jiggery pokery and some looking back through archived
Adobe pages. I'm assuming Adobe just dropped support for IE7 at either
FlashPlayer 13 (maybe 12, as I couldn't find an archive of the requirements
page for
We are currently running Flex SDK 4.6 and have rolled out FlashPlayer 11.1 to
our clients.
We want to support the native right-click customisation functionality
introduced in 11.2. We also have a requirement to support IE7.
Looking through the release notes for each version, when I look at 11.2
Ok, so I've modified the code to eliminate JabbyPanda's DataField4 component
and creat mx:DateField controls instead.
Modifying the steps so that I create and remove a DateField before taking
snapshot, then doing it again I still get the following stuff loitering:
Took your advice and created a test app that adds and removes DateField4
components, directly and onto a comparative ExplorerBar component for
experiments.
Now, last time I tried to show some code on here directly all the CDATA
stuff couldn't be seen. So I've uploaded it as a files this time
Yes, unfortunately the FlashProfiler can only take me so far before I have to
switch to Scout and as you rightly say it's not so good for locating what is
holding references.
So some background first.
Explorer is an Actionscript component extending VBox. It's added to a
SuperTabNavigator
Played around, commenting out stuff and think I've found what's pinning it.
The Explorer has an ExplorerBar, which contains a bunch of navigation
buttons and a view date component. That date component is one of ours and is
a subclass of mx:DateField (actually a subclass of
Great suggestion. Might do that to track down the problem as I have proved
something else.
After investigation we are using the 0.5.swc of
com.jabbypanda.controls.DateField. This has not been touched or even looked
at within our system for YEARS. Looking online there is a 0.51 of this
component
DarrenEvans wrote
Great suggestion. Might do that to track down the problem as I have proved
something else.
After investigation we are using the 0.5.swc of
com.jabbypanda.controls.DateField. This has not been touched or even
looked at within our system for YEARS. Looking online there is a 0.51
Yup using that with mixed success.
jmclean wrote
Have you tried clicking on the Force Garbage Collection icon (the garbage
bin) in memory allocations tab? I find that usually narrows the issue down
quite quickly.
--
View this message in context:
Thanks Alex, useful information.
The scenario we have is perform a bunch of steps and the memory just keeps
on going up never to come back down. Do it enough and the application
crashes, which is what the customers are reporting.
Our application has a ShellBody and in that we have a
Yes, read that, it was one of the first ones. Gives a reasonable overview on
how memory is allocated but doesn't really get down to the details of
working with the results Scout gives to locate leaks.
In our application's architecture we have a common framework and then the
main application sits
Following on from my enabling advanced telemetry thread, I am now getting
lots of lovely information coming from Adobe Scout.
I've used this tool before quite successfully to remedy some performance
problems. However, using it to locate memory leaks is leaving me scratching
my head in confusion
Harui wrote
There should be an additional SWF tag. If you save the output to two
different files and run a diff, are there any differences?
On 8/22/14 10:06 AM, DarrenEvans lt;
darren.evans@
gt;
wrote:
Ok, not used SWFDump before. Downloaded and ran it against the SWF file in
question
That's why I askedI'm stuck on Flex 4.6 SDK and cannot move up due to our
usage of an ILOG Elixir Component... so will it output anything for a
SWF compiled using 4.6?
If I retry enabling the SWF through the air app again it apparently detects
Telemetry is on Dunno if that actually
I better go back to basics here as my output from SWFDump doesn't look like
that.
I downloaded from: http://www.swftools.org/
I'm thinking this is not the SWFDump you are referring to? Where can I get
it from?
jmclean wrote
Adobe Flex 4.6 didn't support advanced telemetry, but you can use
Ahh didn't realise it was a standard thing packaged with the SDK.
SWFDump confirms the advanced telemetry flag is set to true.
A slight bit of progress.I think IE was caching the SWF file and using
that (which didn't have the telemetry on). I've purged all versions from the
cache and now
OmPrakash Muppirala wrote
ILOG Elixir compatibility issue was fixed in 4.11. So, if you get the
latest SDK, I.e. 4.13, you should be good.
Somebody else mentioned this a while back when I had another issue.
At that time, I took the latest SDK (which was 4.12 I think) and the same
problems
Trying to sort the wheat
from the chaff here and cannot for the life of me see what's not being
deallocated. Just seems to be a big list of allocations and how much they
used and you can't seem to see if it's been garbage collected or not.
DarrenEvans wrote
What am I missing now?
--
View
Hiya,
We have a memory leak in our application and I'm trying to get Adobe Scout
working against it so I can start analysing what is happening with the
memory.
We are stuck on Flex SDK 4.6 and using IntelliJ to compile with, so
compiling with -advanced-telemetry=true is not an option (as far as
3:39 AM, DarrenEvans lt;
darren.evans@
gt;
wrote:
Hiya,
We have a memory leak in our application and I'm trying to get Adobe Scout
working against it so I can start analysing what is happening with the
memory.
We are stuck on Flex SDK 4.6 and using IntelliJ to compile with, so
compiling
Hi Maurice,
This is BRILLIANT news!
Will give this a try sometime this week.
Maurice Amsellem wrote
Hi Darren,
ILOG Elixir and Apache Flex compatibility issue has been fixed.
See https://issues.apache.org/jira/browse/FLEX-33421
So there is one less huge reason for not moving your
Doesn't need any data, requiredVsActualDataProvider is a blank array!
private var requiredVsActualDataProvider:Array = [];
I've ruled out actual data being the problem.
Can't running the basic profiler as it just crashes because the application
is so bigand not set up Scout in a while (last
Here is full code to highlight the problem. This example takes about 5
seconds when you press Setup Axis:
?xml version=1.0 encoding=utf-8?
s:Application xmlns:fx=http://ns.adobe.com/mxml/2009;
xmlns:s=library://ns.adobe.com/flex/spark
It's showing on my post here.Don't know whether it got removed because it
was in a CDATA block
It's simply:
import mx.charts.LinearAxis;
private var requiredVsActualDataProvider:Array = [];
private function
-Message d'origine-
De : DarrenEvans [mailto:
darren.evans@
]
Envoyé : mardi 18 mars 2014 15:50
À :
users@.apache
Objet : RE: Patching Flex 4.6 SDK chart functionality
Hi Maurice,
Thanks for helping out too.
Moving to anything above 4.6 is impossible without severe
As I mentioned, I have inherited this code and the interval was already being
set.
I do not see the need for an interval of 0.1. I think it will be ok to
remove it. The 0 to 100 min/max is purely for example. In reality the data
will range from 0 to 8 (maybe up to 10) so an interval of 0.1 is
Our application is a big stack of modules culminating in Client application
as the top level binding them all together.
Do I need to add the -static-rsls=false compiler option to all modules or
just the top client level?
--
View this message in context:
After posting a comment on
https://sourceforge.net/adobe/flexsdk/wiki/Flex%204.6/
https://sourceforge.net/adobe/flexsdk/wiki/Flex%204.6/ and being kindly
answered by Alex Harui, he directed me here to continue.
For a bunch of reason we are stuck on Flex SDK 4.6 for the forseeable
future.
The
53 matches
Mail list logo
