Flash CS3 Documentation |
|||
| Developing Flash Lite 1.x Applications > Testing Flash Lite Content > Errors | |||
The Adobe Device Central emulator can generate alerts as you test your content. One type of alert appears only in the emulator and is intended to provide information about actual or potential errors; the other type of alert occurs in both the emulator and on an actual device.
The first type of alert provides debugging information about your SWF file. For example, if your SWF file contains ActionScript that isn't supported by Flash Lite (or by the version of Flash Lite available on the currently selected test device), the emulator generates an alert.
The other type of message that can occur in the emulator also occurs on an actual device. These types of errors are displayed in an error dialog box that the user must close for the application to continue. The following image shows an example error dialog box as it appears in the emulator:
On a device, the error dialog box that appears contains the string "Problem with content" followed by an error number. In the emulator, the error dialog box also contains a short error string. The emulator also displays a longer description of the error in the Output panel.
The following table lists all the errors that occur in the Flash Lite player, including error numbers, the short descriptions that appear in the error dialog box, and the longer descriptions that appear in the Output panel:
|
Error number |
Error string |
Description and possible causes |
|---|---|---|
|
1 |
Out of Memory. |
The emulator has run out of heap memory. Unless otherwise specified, the emulator allocates 1 MB of memory for a SWF file to use. |
|
2 |
Stack Limit Reached |
The emulator has detected that its stack limit has been reached or exceeded. This could be caused by various reasons, including multiple levels of nested movie clips or complicated vector drawings. |
|
3 |
Corrupted SWF |
The emulator has detected that the SWF data is corrupted. |
|
4 |
ActionScript Stuck. |
The emulator has detected that certain ActionScript code in the SWF file is taking too long to execute. As a result the emulator has stopped executing the ActionScript code. |
|
5 |
ActionScript Processing. |
The emulator has detected an ActionScript error, such as a reference to a nonexistent movie clip. |
|
6 |
ActionScript Infinity Loop. |
The emulator has detected an infinite loop or deeply nested ActionScript (for example, deeply nested |
|
7 |
Invalid Frame Buffer |
The emulator has detected an invalid frame buffer. |
|
8 |
Invalid Display Rect |
The emulator has detected an invalid display rectangle. |
|
9 |
Invalid Frame Number |
The emulator has detected that the SWF file has attempted to move to or resolve an invalid frame number. |
|
10 |
Invalid Key |
The emulator has detected an invalid key input. |
|
11 |
Bad JPEG Data |
The emulator has detected that JPEG or PNG data in the SWF file is corrupted, there is not enough memory to decode the JPEG data, or the format of the JPEG data is not supported. |
|
12 |
Bad Sound Data. |
The emulator has detected that the SWF file contains an unsupported sound data format. |
|
13 |
Root Movie Unloaded. |
The emulator has detected that the root movie has been unloaded and was not replaced with another SWF file. |
Flash CS3