We have created a publication which uses several HTML animated charts. While the experience is good on iPad 2 (except for the anoying delay for html content loading), when we tested on iPad1 resulted on the app crashing several times. Is there anyone else that has this experience between iPad 1 and 2?
Do you know a fix for this so the HTML content doesn't crash the app?
I can confirm that the iPad1 is dramatically slower in rendering HTML
content than the iPad2. you can only try to make your HTML more efficient
(by using less libraries) and reducing the number of HTML on the articles.
or disable autoplaying: my ipad crashes often when I preload 3 or more Edge
animations in one long article.
I am having a similar problem. Two iPad 1's crashing randomly in locations but every time on an app that is a simple black and white text in three book/articles. However each page has an mp3 narration file that autoplays on load. Three articles, 45 pages each with an mp3 files averaging 300k-500k each (120 files/total app 50megs). I added a delay on the autoload. Audio files are on the page using overlay creator and a simple controller skin.
This was not happening last early march in a similar app we made for testing, or maybe we are just testing this one more as we are ready to launch.
I am using CS5.
Further to Above, the app does not seem to be crashing on an Android Samsung Galaxy running out of Content Viewer.
On the iPad I recompiled a new fresh app in V21 but same crashing. I submitted a tech support request but would appreciate any ideas or feedback here.
Sometimes the Adobe Viewer, or a custom Viewer, appears to crash. However, the iOS is in fact shutting it down because of a low memory state. You can confirm whether you have this issue by syncing an affected iPad to a Mac. Then retrieve the logs to see if there are LowMemory-[time stamp].log files. Here is where such log files, as well as crash log files, is found:
Users/[user name]/Library/Logs/CrashReporter/MobileDevice/[device name]
Look for a LowMemory log file with a time stamp that corresponds to the application's exit. Open it in a text editor and look for a line like the following:
viewer <42d0b24207f7d625b2fefef7549afce3> 33490 (jettisoned) (active)
The numbers can vary. However, if the line indicates that the "viewer" process was "jettisoned" while "active," the OS closed the process because of a low memory state. The most likely reason for this is that your viewer is reading into memory images that are larger than 1024 x 1024. Apple recommends against applications loading any image larger than this size as it contributes to a low memory state on the device. It can result in what appear to be application crashes. Review your folio source files and ensure that no images of greater size are used. If they are, simply resample them, and republish your content.
The low memory state can also be the result of having too many applications running at once. Shut down applications you are not actively using to free up more memory.
How to free up memory on your iPad
1. From the home screen, double-click the Home button to display recently used applications.
2. Tap and hold one of the applications until a red minus appears above it.
3. Tap the red minus for all apps that are not currently needed.
4. Tap anywhere above the list of recently used apps, to return to the home screen.
Please see post at http://forums.adobe.com/message/4589295#4589295
I performed all the above and rebuilt the apps and they still crash. There appears to be an issue with newer viewers on older iPad 1's
Adobe DPS Technical Support called ME about this, made it a priority one case and sent it to engineering with my sample files. I almost passed out from shock!
They said it is a problem in recent versions (20/21) and that it goes away in version 22.