Compiler Errors This page describes what to do when you encounter the "An internal compiler error occurred" message in Flex Builder. This page includes the following topics: Viewing the error log file Submitting a bug

rate-11076217-75187 User rating? 1 2 3 4 5

Viewing the error log file

The Eclipse error log file stores details about your Eclipse sessions and compiler errors that occur during those sessions. These are not the same as Flex Builder compiler errors, which are displayed in the Problems view.

If you are using the Flex Builder plug-in:
Using the Error Log View, double-click the error item to view it in the Eclipse error log file. Use the Copy button to copy the error item to the clipboard.

If you are using the Flex Builder standalone version:
Select Help > Product Details. Click the Configuration Details button, then click the View Error Log button.

Common errors

• ASC-2839 - Empty switch statement causes null pointer exception. Delete the empty switch statement if it is unneeded; otherwise, add the appropriate "case" clauses inside the braces.

Submitting a bug

The Flex Builder bug database is located at http://bugs.adobe.com/jira. You are not required to log in to the bug database to browse existing bugs, but you must have an account to add bugs.

Before filing a bug, you should search the existing bug database to see if the bug you are experiencing is a known issue and has a workaround, or has been fixed in the next release of Flex Builder.

To submit a bug:

1. Create a Flex project that reproduces this bug. Try to reproduce the bug with as few files and lines of code as possible. The simpler the use case, the easier it is to verify that it is a valid bug.
2. Export the project by using the Flex Builder Export Flex Project Archive feature (File > Export > Flex Project). You will attach the resulting ZIP file to your bug entry.
3. Identify the steps necessary to reproduce this bug with the exported project.
4. Identify the following information about your system:
   • Platform and OS version
   • JVM version
   • Memory configuration (total amount of RAM and total amount allocated to Flex Builder with the <code>-Xmx</code> VM argument)
5. Open the Eclipse error log file and copy the error message that you received.
6. Follow the instructions for submitting a bug.

You can also copy the Configuration Details from Flex Builder to a separate file and attach that file to the bug that you file.

After you submit a bug, you can view its progress in the bug system. The bug will be automatically added to your dashboard page so that you can see it the next time you log into the bug system.