adl startup extremely slow

I am developing an Adobe AIR project, and when I turn on Generate debuggable SWF in the compiler options of my main module, adl startup takes forever. The time between compilation completing and the adl window with my app displaying is over a minute. With Generate debuggable SWF turned off, the time to display is approximately 5 seconds.

Is there anything I can tweak to fix this, or somewhere to begin looking for possible causes/solutions? I am using 11.1.1

Thanks in advance,
Ben

10 comments
Comment actions Permalink

Can you please try to launch your app using adl from command line? If performance is the same as via IntelliJ IDEA (and I suppose it is the same) I'm afraid nothing can be done with this at IntelliJ IDEA side.

0
Comment actions Permalink

Yes, I forgot to mention in my original post that when running from the command line and FlashBuilder startup is nearly immediate. Maybe 3 seconds.

0
Comment actions Permalink

This is something very strange. Is IDEA UI responsive during this minute of doing nothing? Is adl command line already printed in the Run (or Debug) tool window at this time?

0
Comment actions Permalink

Yes and yes. The UI is completely responsive and the Console shows the following output, followed by some trace statements from the app while I wait. Also, adl is launched immediately (shows up in app switcher, etc) but nothing shows up for about a minute.

/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java -d32 -Dapplication.home=/projects/MyClient/Flex4.5.1AIR3/CurrentSDK -Xmx1024m -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Duser.language=en -Duser.region=en -classpath "/Applications/IntelliJ IDEA 11.app/plugins/flex/lib/idea-fdb-4.5.0.20967-fix.jar:/projects/MyClient/Flex4.5.1AIR3/CurrentSDK/lib/fdb.jar" flex.tools.debugger.cli.DebugCLI
Adobe fdb (Flash Player Debugger) [build 21309]
Copyright (c) 2004-2007 Adobe, Inc. All rights reserved.
Waiting for Player to connect
/projects/MyClient/Flex4.5.1AIR3/CurrentSDK/bin/adl /projects/MyClient/AirApp/out/production/MainModule/MainModule-app.xml /projects/MyClient/AirApp/out/production/MainModule
Player connected; session starting.

0
Comment actions Permalink

Additionally, if I create an Ant target to run adl with the same arguments and tell IDEA to run that target before launch, the app launches immediately and I can use it before IDEA even gets around to trying to launch the app.

0
Comment actions Permalink

May be this is caused by some timeout in the Adobe's debugger. Does adl startup performance become normal if you click Run instead of Debug?
Does your app load other swfs or any resources on startup?

0
Comment actions Permalink

Yes, startup is normal with Run instead of Debug. The app does load a stylesheet SWF at startup.

0
Comment actions Permalink

Thanks,
well, we need to debug fdb tool from Adobe Flex SDK (fortunately it is opensourced), but unfortunately we don't have sample project to reproduce the bug. We'll greatly appreciate if you manage to create sample project and attach it to the related issue: http://youtrack.jetbrains.com/issue/IDEA-58648.

0
Comment actions Permalink

If it were a bug in fdb the problem would exist when debugging in FlashBuilder, wouldn't it?

I will try to create a sample project, but am skeptical the issue will be present in that scenario. Also, I do not have access to the youtrack link.

0
Comment actions Permalink

FB doesn't use fdb tool from Flex SDK literally.
You'll get access to the issue as soon as you register in YouTrack.

0

Please sign in to leave a comment.