Crash on iOS with air 3.8 and higher

Hello,
We have an application we are deploying on PC & Mac using the FlashPlayer. We are porting the application on Android and iOS using Air Sdk. The application runs perfectly well in terms of performance. The game runs without any trouble til the end on Android but we are experiencing a crash on iOS.
The crash seems to be related to a memory issue. We profiled the application with Instruments and when the crash appears, the application consumes 90Megs of memory. This is for an iPhone 3GS. On an iPad2, the game crashes similarly around 100Megs of Ram used. The crash log refers to a bad access exception and as we are receiving a lot of low memory warnings, we assume it comes from a malloc that fails.
We obviously don't have any leaks left as the game runs well on all the other platforms. this is especially obvious as the game runs perfectly well on Android with the same sdk. We are rendering in gpu mode. We also tried to switch to cpu without any luck. The garbage collector seems to be triggering well as we can see the live bytes going down regularly depending on the clips being played.
What we don't understand is that the crash log says we are using around 50000 rpages, which corresponds to a total memory of 200Megs (4k per page). This is weird as Instruments tells us the application consumes 90Megs of Ram when the crash occurs.
The only big difference between the iOS and the other platforms is that the swf assets can't be unloaded. Therefore, once loaded, they stay in memory. Still, we tried to use as much movieclip as possible so we can stop them and remove them from the scene when they are not needed. This, to make sure the display data are released as often as possible.
Do you have any kind of advice to solve this issue ? This is becoming quite urgent as the game is finished and this bug prevents us from releasing the master build.
Regards.

Hi Chris,
We found the crash on iOS7 devices. The game native display is 16/9 so depending on the devices screen resolution, we have to apply black stripes on top/bottom of the screen. To make sure nothing bites on those stripes we have a mask applied directly on Lib.current. If we get rid of this mask, no more crash on iOS7.
The funniest thing is that without this mask, we also managed to reach act 6 on iOS6 and lower. Before that we couldn't get pass act 3. We are currently trying to remove all the masks we have to check if this solves our problem.
Does this pop something in your mind ? Could these masks lead to memory leaks on iOS devices ?
Thanks,
Philippe

Similar Messages

Error creating files. Compilation failed... when publishing iOS app with AIR 3.1 and Flash 11.5.1

Hello, I'm running Windows 7. I'm using Flash 11.5.1 (that's CS5.5 updated once) and AIR 3.1 to make an iPhone app.
I can export the app perfectly fine with either Ctrl+Enter or F12.
I added all the required things with AIR for iOS settings, such as a p12 certificate and icon files.
I then hit publish. After I hit publish, I got this error:
Error creating files.
Compilation failed...
I tried dragging the window to see if there was anything hidden behind the elipses. What can I do to fix this problem?

note sure if I'm much help other than to CONFIRM it is working for me by using the sdk WITHOUT the compiler. Check out adobe's little note: "Note : Flex users will need to download the original AIR SDK without the new compiler."
I am using FB 4.7 with AIR 3.6 and seems to compile correctly for iOS.
Maybe try reinstalling flash builder?
I honestly don't know if the JRE has anything to do with it... I'm using 1.7 ....to see what JRE you're using, open the Java Control Panel (I right click my java orange icon and hit properties), select the Java tab, then hit "View..."

The three main hurdles to porting existing Flash projects to iOS with AIR

The purpose of this discussion is to identify significant problems currently preventing AIR for iOS from being a viable solution for porting existing Flash apps. These issues have been largely ignored by Adobe, so I hope that everyone will add to this discussion if you have also run into these roadblocks in targeting iOS with the AIR SDK. I hope that Adobe staff will address and provide some much needed information with regard to fixing these problems.
There are 3 main problems with targeting iOS currently, which are probably affecting anyone who is trying to port a project that is both medium to large in size and makes use of SWF loading. Pretty much any project that has a MVC architecture is going to load SWF assets that are compiled against a view class, so this is likely affecting many people.
1. Bug - ADT packager runs out of memory when packaging "large" numbers of SWF assets
https://bugbase.adobe.com/index.cfm?event=bug&id=3511656
This is a blocking bug that prevents packaging projects with a large number of SWF assets. It is preventing me from being able to package all the needed assets for my project. I provided Adobe with my project to package a couple months ago so this bug can be reproduced in house and fixed. The Adobe employee who was handling this never tried to reproduce the issue and has stopped responding to email and comments in the bug. Adobe, please have someone take charge of testing and fixing this bug. It seems like it would be a straightforward fix once the failure is reproduced within a debugger.
Has anyone who has encountered this problem determined the number of files or classes where it starts to fail. I've spent some time trying to reverse engineer what the packager is doing when it runs out of memory, so think I can determine how many classes it's working with, but obviously the size of the classes will be variable and so this number will probably be more of a range where we start to get into the failure state.
Please let me know if you can reproduce this issue with your project with many SWF assets and upvote the bug if you are already aware of this one.
2. Bug - SWF reloading when doing a "real" (AOT) compile
https://bugbase.adobe.com/index.cfm?event=bug&id=3636385
There is already a forum post that covers the history of this issue (http://forums.adobe.com/message/4920638) but that also covers some issues in older AIR builds with loading of any SWF asset (previously fixed), where this bug deals specifically with reloading of SWF assets that include compiled bytecode (ABC).
The expectation here is that all versions of the Flash runtime should handle SWF reloading with ABC in the same way, so that a single codebase can be used to target web and iOS (or any other platform). This is the only issue of the 3 that has a legitimate work around, in my opinion, because the assets can be cached within the app within a loading manager layer. All the application code that makes loading calls can stay the same, and a compiler flag can be used to enable this caching for iOS builds, with subsequent requests returning a new instance of the cached asset. This can potentially lead to a very bloated memory footprint for the running app after a period of time, though, which could make some apps perform poorly, so a bugfix is ultimately needed.
3. Unimplemented feature (?) - The constraint that a single ApplicationDomain is used when running AIR for iOS
I did ask about this in the same forum post as SWF reloading but didn't get an Adobe response. Why does this constraint exist? My guess is that the AIR runtime for iOS simply hasn't implemented multiple ApplicationDomain support at this point, and that this was done to focus resources on other high priority features for the iOS runtime. It's possible that there is some aspect of the iOS operating system that makes it difficult or impossible to implement this feature, which may be why it's been avoided to this point, but obviously this is all conjecture without hearing from Adobe on it.
This is a major issue that needs to be addressed. For us, the problem is that our SWFs for multiple instances of the same type of asset use the same name for the AS export. For example, each item an avatar can equip is a single SWF with multiple sub assets -- the parts which comprise the item. Each of the parts will have an AS export name based on the avatar facing and where it is equipped, like "fv_head". This naming is consistent across all items, so we will load a lot of assets containing "fv_head" simultaneously. This normally works fine because the default behavior for Flash has always been that each SWF is loaded into a new ApplicationDomain instance, but for iOS a single ApplicationDomain must be used, causing these names to collide. The last SWF loaded containing a given AS export name overwrites the previous ones of that name.
The work around for this, and I use that term loosely, is to go through and uniquely name every AS export in every asset where sets of assets with the same export name is used. For us that is hundreds of items with multiple exports. Maintaining unique naming across all these parts is also a very error prone process, not to mention all the code that manipulates the parts needs to be modified to handle the new naming and make sure it's referring to the now uniquely named assets.
The expectation here is that all versions of the Flash runtime should handle asset loading in the same way and place each loaded asset into its own ApplicationDomain container as the default behavior. I'd like an Adobe employee to address my assumption that this is an unimplemented feature of AIR for iOS at this point, and let the community know if a solution for this will be implemented.
Summary
All three of these issues in combination are a major roadblock to porting existing Flash games to iOS with AIR. Issues with one can make it hard to test and try to work around others. All need to be fixed, but If I could only pick one of these to fix, it would have to be issue 3 -- that lack of proper ApplicationDomain support when loading assets. This issue is completely inconsistent with standard Flash behavior and creates a major roadblock to ports of existing applications with no viable solution for a workaround.
I look forward to Adobe's feedback on each of these issues and hopefully fixes that will allow those of us working with AIR for iOS to get our products to market.

About the 3rd issue being an AoT design limitation, I'm not sure I understand why it's necessary to know during AoT packaging what the domain is that a child will be loaded into to be able to have SWF loading work as on the browser.
Isn't the ApplicationDomain an internal construct in the AIR runtime that you guys define in order to manage namespaces of loaded SWFs? To be clear, when I say "runtime" I know that the resulting code isn't being interpreted within the iOS app, but clearly you have a set of AIR libraries that get compiled into the IPA that provides support for all the Flash APIs. If that's the case, then wouldn't it be possible for the iOS version of the AIR libraries to define a new ApplicationDomain on the fly when code that has been cross-compiled to iOS native code loads a packaged SWF?
I don't have a clear picture of how ApplicationDomains are managed internal to the runtime of course, but a little more detail would be very helpful. Thanks.

HT202157 My AppleTV (2nd gen) crashed last night with the latest update and now all I have a flashing light. What to do?

My AppleTV (2nd gen) crashed last night with the latest update and now all I have a flashing light. What to do? It showed a USB symbol point toward an iTunes symbol and won't reset after resetting with the remote. Same thing.

usb symbol pointing toward an itunes symbol is apples way of trying to get you to connect the appletv to your computer running itunes so it can restore the apple tv's software
though it seems to be a connection few people make

IPhone 4 crashed during ios update (5.0.1) and won't restore. anyone know how i can get my iPhone working again?

iPhone 4 crashed during ios update (5.0.1) and won't restore. anyone know how i can get my iPhone working again?

Try to force your phone into recovery mode. Disconnect it from the computer's USB cord. Turn it off if you can by holding the sleep/wake switch until you see the red slide to off. If you can't turn it off, please continue. Press and hold the home button while plugging it into the computer's USB cord. Continue holding the Home button while iPhone starts up. While starting up, you will see the Apple logo. When you see "Connect to iTunes" on the screen, you can release the Home button and iTunes will display the recovery mode message. See http://support.apple.com/kb/HT1808 for details.
Then you can restore your phone: http://support.apple.com/kb/HT1414

No more Uncompiled ActionScript warning on iOS with AIR 3?

Hi!
With previous versions of Air on iOS, when I was loading an external SWF that was containing library symbols using linkage names, I was getting a popup message saying that uncompiled actionscript was not allowed on this system. It was really a pain, since it was not possible to use the class system of AS3 to instanciate several instances of the same object. So I had to create all the instances on my stage in the IDE, and manipulate them using GetChildByName() in my pure AS3 code.
Today I made some tests, and didn't realize that my SWF file was containing some symbols with a linkage name. And it was working fine! With previous versions of AIR, I was getting an instant warning message, and the app was stuck.
So I made further tests, and now I can load an external SWF even containing AS3 code on the timeline, and it works!! Really I don't know what to think. This is wonderful news, because now we can really implement iOS apps the same way we would on any other platform. But I also know that this previous behaviour was due to some security reasons, to prevent apps made with AIR to download some external malicious code contained in an external SWF.
So my question is: is it allowed by Apple, or will my app be rejected? Or maybe this limitation is now applied to really external SWF (like something hosted on a remote server), and AS code is accepted for SWF files that are packaged locally into the app?
I'd really like to have Adobe employee's feedback on this, please.
Thank you!
Frédéric

Doh, you're right, I was doing interpreter builds, my apologies... I had forgotten that in interpreter mode, AIR doesn't display any warning... Which makes me think that Adobe may put that restriction on all targets by the way. Someone could develop all his game in interpreter mode, just to realize that the normal AS3 instanciation approach doesn't work when switching to final target...
As a side note though: when switching to ipa-app-store target,with AIR 2.7, my game hangs at startup, when loading the external SWF. But with AIR 3, the game seems to load fine but my movieclip is not displayed at all, as if AIR was just discarding silently all unauthorized behaviours... (actually the app behaviour looks erratic, so it must crash silently, trying to continue excecuting code). If it's the case, it might be even more confusing for people who are not aware of this restriction.

Our EnergyWatch app crashes on Android with AIR 3.8

Please help!
We have been running an Android app - EnergyWatch - (available on Google Play) for about one year now. Suddenly after customers having received the 3.8 AIR upgrade the app crashes during initialisation. We are using Secure Socket API for communication, and USB debugging tells me that the app seems to crash just before it receives the ON_CONNECT event.
Everything still works fine on iOS (still runnning an older, embedded AIR runtime)
Everything also works fine on Windows with AIR 3.8 installed.
I've tried two different builds:
Flash Prof. CS 5.5, with AIR 2.6 (same build environment as the current version on Google Play)
Flash Prof. CS 6, with AIR 3.4.
Exactly the same behaviour on both builds.
I really don't know what to do.
1. Are there any changes made to the Secure Socket API, especially on Android?
2. Could we recommend our users to downgrade the AIR runtime? If possible, where can we find the previous runtime version?
Tomas Öquist
Perific Technologies AB, Stockholm, Sweden

HI, Tomas
     may i give you an advise?
   If you really want your app run stable . PLZ package with "captive runtime" .
In my experience. Adobe guys will change API Behavior ,change API ,change everything random except themself .   Do you remember the ShareObject behavior changed at AIR3.5.
since they cann't be trusted , you should always embeded AIR runtime . for your users, for yourself ,especially for adobe .
For all of AS3 developer ,God ,please bless us.
Raymond

Sounds stop playing when user locks screen on iOS with AIR 3.9 Beta

We built a simple application that should play sounds when in background and when the screen is locked.
Since we updated to the latest AIR 3.9 Beta SDK, all sounds stop playing when the user locks the screen on iOS.
The sounds resume when the screen is unlocked.
- it works on Android
- we use renderMode : cpu
- we use UIBackgroundModes : audio
- we use NativeApplication.nativeApplication.systemIdleMode=SystemIdleMode.KEEP_AWAKE;
- sounds play when the app is in background
- was working great with AIR 3.8 SDK
Any help would be greatly appreciated.
Thanks!

Thanks for reproting the issue, we have an internal already logged bug for this, which is under investigation at the moment.
-Nimit

I have a biggest glitch of the new iOS 7 i don't know what is it but yesterday i've noticed my iphone 5 2% of battery i started to charge it and it stucks on 2% and then is started to crash my iOS again some color stripes and then crash

And then it works somehow by electricity BUT it stucks on apple logo (white screen with the black apple logo in the middle) and after 5 seconds it dissapears and then it poppin up again and again disappears and this keep to going like ths unti i do something like turn iphone down and hold the cable and it shows battery with the red color in the beggining (it says in EVERY apple davice that you need to charge your battery to continue to work with your device but HOW????I left it on charge ALL night while i was sleeping how it couldn't be charged at least for 8%??) and also my iphone is doesn't turning on without cable,when i taking off the cable it doesn't work again i hold top button and it doesn't work,holding home button and power top button doesn't work too,trying to plug it to my PC it still not working i see only black screen and no more than this it works only with the simple elctricity and not by PC but always i see my lock screen it shows 100% i taking off the cable and it's like you taking off PC cable while you're working on it and it shutting down immediately so it looks the same on my iphone like USB is a power cable of my iphone please help me.
P.S. Updated to iOS 7 first time via iPhone 5 itself but i needed to restore and update it via iTunes because of push notificaton issue.

Reset the device:
Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears.
If that doesn't help, tap Settings > General > Reset > Reset All Settings
If nothiing above helped, restore the iPhone to factory settings > Use iTunes to restore your iOS device to factory settings

Flash Pro CC 2014 Crashes When Publishing with Air

While trying to publish my app with Flash Pro CC 2014 the program crashes. I'm using the current Beta version of AIR 15 (previous version had the same results) on a Mac (Yosemite OSX 10.10 beta 5, Not the public beta) . When I publish to just a swf file there is no problems. If I publish to Android, iOS or Desktop then Flash crashes. When the Adobe crash scene comes up I do submit the reports to Adobe. At the end I get a message telling me Adobe found a solution for the recent crash and to "click here" for further details. When I do it just goes to the Adobe home page with no help. Is there a solution or workaround? I've been using one of my other machines that has Mavericks on it for publishing for the time being. I would like to work at one machine and not transferring back-and-forth. Any help will be great!

The updates are not available @ http://www.adobe.com/support/flash/downloads.html#flashCC
The updates are available through Creative Cloud desktop app or through in-app update option.
You can also try by launching flash professional CC 2014 version you have installed and go to Help->Updates. This should ideally do it.
Incase, it is not updating after this, can you please let me know the type of Creative Cloud license that you own?
Do you belongs to an environment where Installation / update of applications are managed by IT team? In that case, please check with your IT team for how to get the latest update.
Rgds,
Mukesh

App Updater Crashes on MacOS with Air 3.9

We just released a new version of our desktop Air app, nothing different with any of the configuration files except for a higher version number. One of our Mac users (10.8.5) who had already updated to Air 3.9 sees the auto updater dialog and it appears to download the new version but then immediately crashes and does not come back. I went to one our our Macs (10.8.5) that did not have the 3.9 Air update and ran the updater and it ran successfully as normal with no problems. I then uninstalled the newest build of our app, updated to Air 3.9, reinstalled the old version of our app, and ran the updater again and experienced the same crashing problem as the other Mac that had already updated. Testing with and without the Air 3.9 update on Windows 7 and 8 does not yield any problems.
Does anybody have any suggestions?

Could you please open a new bug report on this over at bugbase.adobe.com? When adding the bug, it would be great if we could get copies of both the new and older versions of your application. If you'd like to keep this private, feel free to email the installers to me directly ([email protected]).
Once added, please post back with the URL and I'll start our internal investigation.
Thanks,
Chris

BUG - rotation of Default image on iOS with AIR SDK 16.0.0.250

Hi guys!
I just switched to AIR SDK 16.0.0.250. Everything was fine except one very strange problem with Default images on iOS devices.
My app runs in landscape mode. In my app I have default images that are shown during application loading phase.
When app start, first I see Default image properly, that for a very short period of time I see Default image rotated 90 degree and scaled to fill the screen and then it disappears and application is get loaded.
Here is a video that illustrates the problem: http://youtu.be/Ry1l1v7dQss
That is very strange, so I want to know if anybody else knows how to handle this issue and what could the source of it? Some info that might help: Application descriptor:
<initialWindow>
    <content>SWF file name is set automatically at compile time</content>
    <visible>true</visible>
    <aspectRatio>landscape</aspectRatio>
    <autoOrients>true</autoOrients>
    <fullScreen>true</fullScreen>>
    <renderMode>direct</renderMode>
    <softKeyboardBehavior>none</softKeyboardBehavior>
</initialWindow>
List of default images:
Default.png
[email protected]
[email protected]
Default-Landscape.png
[email protected]
So, for me it seems like a bug in AIR SDK 16.0.0.250, on AIR SDK 15.XXX everything was just fine.

Thanks for reporting the issue. Yes, It's known to us and we are investigating it.
Best Regards,
Jitender

Hard drive crash need help with new iTunes load and backup files

I have looked through the posts and not found my situation.
I had my iPhone synced to a PC computer and the hard drive crashed. I had an extensive library in iTunes, but none of the music was purchased online so I can't simply download it again. It was all from CD's, many of which belonged to friends. I now have an iMac. The music I like is still on my iPhone, but not on my new iMac. When I try to sync the iPhone with my iMac it wants to delete all the music on my iPhone. Is there any way to copy the music off my iPhone first - so I can add it back into my iTunes library?

Yes, luckily I have been in this situation.
You can download a free application that will take your music from your iPhone and place it onto your Macintosh HD.
One of these should suit your needs:
http://www.macupdate.com/app/mac/19890/ipoddisk
http://www.wideanglesoftware.com/touchcopy/index.php?gclid=CPjvvOiyr6gCFaNl7Aodm h6QIQ
http://www.headlightsoft.com/detune/
I hope this helped.

Hard Drive Crash - need help with choosing new drive and installation

My hard drive seems to have crashed. My computer froze, and when I tried to reboot, it got stuck at the startup screen. I started from the system CD, ran the disk repair utility, and it said it could not repair the disk. I ran Tech Tool Pro and it could not repair the disk. I tried to start up in Target disk mode while connected to my older G4 iMac (that I'm using now as my backup), and the disk would not mount. So I need some expert advice - I am assuming the hard drive is toast. I wish I could at least mount it in target disk mode to transfer files, but I haven't been able to do that. I was going to take it in for repair (or possibly buy a new computer), but after reading some of the posts here, I am thinking I could just replace the internal hard drive with a 3.5" SATA drive.
What I need to know is am I correct about this? And is this the right kind of drive for my iMac? Are there any specifications I need to be aware of when ordering a new drive? I downloaded the manual explaining how to replace the drive and it looks doable. I would appreciate any guidance as to choosing the new drive (specific brand names/models would be great), installing the drive, and tips for formatting, etc. Thanks in advance for your help!

Welcome to Discussions - any 3 1/2" SATA drive will be fine, go to [macsales.com] or [smalldog.com] or [newegg.com] and choose whichever drive fits your wallet. Most of them are reliable, I have heard of problems with Seagate and Hitachi, but there are always some failures with any brand. Make sure to get a good warranty.Instructions will come with the drive, but you can download them from [Apple|http://www.apple.com/support/manuals/imac> as well.

Firefox 16.0.1 Crashes, Not Responding with Unresponsive Script Warnings and Adobe Flash Plugin Crashes

Hello,
I'm experiencing some issues with Firefox 16.0.1 which I had also experienced with Firefox 15.0.1.
On numerous occasions Firefox has crashed while attempting to access a website link contained in an AOL e-mail message.
Unrelated to that issue, Firefox has hung up frequently with associated unresponsive script warnings and occasionally with the Adobe Flash Plugin crashing. Some of the unresponsive script warnings are:
http://connect.facebook.net/en_US/all.js:127
http://e.huffpost.com/elections/assets/pregeneral_rr.js?d2e0923f3d19471c9e93c391a701ef30e3f427e8:1
http://o.aolcdn.com/cdn.webmail.aol.com/37001/js/dojo-custom/dojo/dojo.xd.js:102
http://o.aolcdn.com/cdn.webmail.aol.com/37001/js/dojo-custom/dojo/dojo2.xd.js:14
http://o.aolcdn.com/cdn.webmail.aol.com/37043/js/dojo-custom/dojo/MessageList.xd.js:52
http://o.aolcdn.com/cdn.webmail.aol.com/37092/js/dojo-custom/dojo/dojo.xd.js:102
http://o.aolcdn.com/cdn.webmail.aol.com/37092/js/dojo-custom/dojo/dojo.xd.js:122
http://o.aolcdn.com/cdn.webmail.aol.com/37092/js/dojo-custom/dojo/dojo2.xd.js:516
http://o.aolcdn.com/cdn.webmail.aol.com/37092/js/dojo-custom/dojo/dojo.xd.js:70
http://o.aolcdn.com/cdn.webmail.aol.com/37092/js/dojo-custom/dojo/dojo3.xd.js:45
http://o.aolcdn.com/cdn.webmail.aol.com/37092/js/dojo-custom/dojo/dojo3.xd.js:76
http://q.aolcdn.com/cdn.webmail.aol.com/37001/js/dojo-custom/dojo/dojo2.xd.js:940
http://partner.googleadservices.com/gampad/google_ads_gpt.js:12
I've reset Firefox and disabled all the plugins and yet these problems persist.
What are those script warnings actually telling me and are there any recommendations on how to resolve these issues?
Thank you,
Mike

You can check for problems caused by recent Flash updates and try these:
*disable a possible RealPlayer Browser Record Plugin extension for Firefox and update the RealPlayer if installed
*disable protected mode in Flash 11.3 and later
*disable hardware acceleration in the Flash plugin
*http://kb.mozillazine.org/Flash#Troubleshooting
*https://support.mozilla.org/kb/flash-113-doesnt-load-video-firefox

Crash on iOS with air 3.8 and higher

Similar Messages

Maybe you are looking for