Flash Lite error and warning messages (Flash Professional only)

The Flash Lite emulator generates two types of error messages while you test your content. One type of message appears only in the emulator and is intended to provide information about actual or potential errors; the other type of message occurs in both the emulator and on an actual device.

The first type of error message provides useful 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 a warning message in the Output panel that alerts you, as the following image shows:

For a full list of debugging messages and their descriptions, see Flash Lite emulator error and information messages (Flash Professional only).

The other type of error 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 of 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 is 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 file 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	N/A	N/A
6	Bad image data	The SWF file contains an image that either Flash Lite, or the platform's native image decoder, was unable to decode.
7	Bad sound data	The SWF file attempted to load a sound in an unsupported format, or the sound data is corrupted.
8	Root movie unloaded	This error occurs when the root (level 0) SWF file is replaced with another SWF file.
9	N/A	N/A
10	getURL string too long	The URL string in the getURL call is too long.
11	Not enough memory to decompress image.	Flash Lite does not have enough memory to decode an image in the SWF file.
12	Bad SVG data	Flash Lite attempted to load SVG data that is corrupted.
13	Stream loading out of memory	Flash Lite does not have enough memory available to handle the data being streamed from a URL. For example, this error can occur if you attempt to load an XML file over the network that's too large for Flash Lite to handle at one time. If possible, try breaking the data file into several smaller files and then load each file individually.