Reporting an error or crash in Aptana [edit]

Report problems in the Aptana ASAP Issue Tracker.

Contents

JVM Terminated

When this happens, you'll get a rectangular dialog with a simple title of "JVM Terminated" and Aptana will disappear. This indicates Java itself has crashed, but it has left behind a log file of what occurred.

By default, the crash file should be in either the Aptana program directory, or in the system temp directory, most likely with an extension of *.hs. If you still cannot locate it, follow the directions here:

You can also find some more troubleshooting ideas here:

Once you have located that file, make sure you submit it to ASAP so that we can fix the issue.

Other Errors

If Aptana fails at startup with a dialog box, or behaves in an unexpected manner, it's highly likely that an error occurred and was written out to the log file. Please follow the directions here to find your log file:

And then add that as an attachment to a ASAP ticket, or snip out the relevant sections.

Using the Aptana Console

If Aptana does not appear to work properly, you can try and use the console to figure out what is happening.

  1. Add -console to the launch arguments for Aptana or Eclipse
    1. On Windows, you can create a shortcut, and add that to the properties of the shortcut.
    2. For OS X, follow he directions below:
      1. Navigate to the Applications folder. Open the Aptana Studio folder.
      2. Right-click (or control-click) on the Aptana Studio application. Choose "Show package contents".
      3. Navigate to Contents/MacOS/AptanaStudio.ini.
      4. Edit AptanaStudio.ini, and add -console at the very top of the file on a separate line.
      5. Save the file.
      6. Close any folders you just opened.
      7. You can follow the same procedures on Eclipse. The folder structure will be identical, and look for the eclipse.ini file
    3. On Linux, it is recommended you start Aptana/Eclipse on the command line and jsut add -console as a launch argument
  2. Once the application launches, you will see a separate console window start. Type 'ss' (no quotes) at the command prompt.
  3. It will show you a list of bundles. Pick the one which is not starting. If you don't see any Studio features at all, you might pick com.aptana.ide.core.ui. Note the "bundle number". See if the bundle says "Started".
  4. If not, type 'start #', replacing # with the number you just saw above. Note any error message displayed and log that with a ticket in ASAP.

Related Topics