If the answers here don't fix the problem for you, please file a support request in ASAP--your bug reports help us improve Aptana Studio and our other offerings.
You can get directly to ASAP from the Help menu in Aptana Studio by choosing Submit Aptana Bug or Feedback from the Aptana Troubleshooting submenu.
Accessing the Error Log
The Aptana .log file records most application exceptions that occur while you are using the Aptana application. The .log file can be helpful to the Aptana development team in troubleshooting bugs that you may encounter during normal usage. You can access your log either through the Help menu in Aptana or manually through the file system on your computer.
Accessing the log from Studio/Eclipse
The Aptana Troubleshooting menu on the Studio/Eclipse Help menu has an option to view the log file. Choosing it opens the log in an editor window, which you can save to a separate file in order to attach it to an ASAP ticket.
Accessing the log manually
Your current .log file is located in a .metadata folder in your current workspace directory.
- Windows XP: C:\Documents and Settings\username\aptana\workspace\.metadata\.log
- Windows Vista: C:\Users\username\Documents\Aptana Studio\.metadata\.log
- Mac OS X: ~/aptana/workspace/.metadata/.log (this is often in the folder for your username)
- Linux: ~/aptana/workspace/.metadata/.log
If you changed your workspace from the default location (see Switching your workspace), the .log file will be in a .metadata directory in your workspace directory.
After a crash, the splash screen appears briefly and disappears
We've seen this issue periodically with Windows users. If you experience this issue, try the following workaround:
- Navigate to the folder where you have Aptana Studio installed (usually under C:\ Program Files), and find the jre folder
- Rename the jre folder to jre.old
- If you have another instance of the latest JRE installed on your machine, skip to the last step
- Download and install a new instance of the JRE from Sun
- Start Aptana Studio.
How do I install Studio updates, with error: Network connection problems encountered during search?
Follow the instructions at the Aptana Studio Update Site.
Can I request a new or changed feature?
Absolutely! This helps us plan and prioritize features to include in upcoming product releases. To let us know what you want open an enhancement request ticket for the appropriate product in ASAP
JVM Terminated
When this happens, you'll see a rectangular dialog with a title of JVM Terminated on your screen and Aptana Studio will disappear. This indicates Java itself has crashed but it creates a log file in the process.
By default, the crash file should be in either the Aptana Studio 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:
- Finding your Error Log
- On the Macintosh, the location is ~/Library/Logs/Java/*.crash.log or ~/Library/Logs/CrashReporter and the file will have the word java in its name.
You can also find some more troubleshooting ideas here:
Please attach this log if you submit a ticket in ASAP.
Using the Aptana Studio Console
If Aptana does not appear to work properly, you can try and use the console to figure out what is happening.
- Add -console to the launch arguments for Aptana or Eclipse
- On Windows, you can create a shortcut and add that to the shortcut properties.
- On OS X, follow these instructions:
- Navigate to the /Applications/Aptana Studio folder in Finder.
- Right-click (or control-click) on AptanaStudio.app and choose Show package contents.
- In the new Finder window navigate to Contents/MacOS.
- Edit AptanaStudio.ini: insert a new first line with only -console on it and save the file.
- You can follow the same procedures on Eclipse. The folder structure will be identical but the file to edit is eclipse.ini.
- On Linux, we recommend that you start Studio/Eclipse from the command line and add -console as an argument.
- After the application launches you'll see a separate console window start. Type ss at the command prompt in this window and you'll get 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".
- 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.
How do I repair my Aptana Studio installation?
If you've just reinstalled Aptana Studio after uninstalling an older version and you get an error in your log file that looks like the following excerpt, you need to repair your installation.
!SESSION 2007-06-05 18:03:17.484 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_01 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB Framework arguments: C:\Program Files\Aptana\Aptana IDE Beta\Aptana.exe Command-line arguments: -os win32 -ws win32 -arch x86 C:\Program Files\Aptana\Aptana IDE Beta\Aptana.exe !ENTRY org.eclipse.core.runtime 2007-06-05 18:03:19.640 !MESSAGE Product com.aptana.ide.rcp.product could not be found. !ENTRY org.eclipse.osgi 4 0 2007-06-05 18:03:19.671 !MESSAGE Application error !STACK 1 java.lang.RuntimeException: No application id has been found.
Repair your Aptana installation:
- Windows: Navigate to C:\Documents and Settings\Username\Application Data\Aptana\Aptana Studio and rename the configuration folder under Aptana Studio to configuration.bak or another temp name.
- OS X: Navigate to ~/Library/Application Support/Aptana/Aptana Studio and rename the configuration folder under Aptana Studio to configuration.bak or another temp name.
If that still doesn't work, you'll need to delete and reinstall Aptana Studio.
How do I stop Studio from loading a problem file?
A file might be causing trouble when Aptana Studio is restarted because it's very large or in some way corrupted.
- Rename the problem file, which will mean Studio cannot find it and so ignore the file on restart
- Delete the <Aptana_workspace>\.metadata\.plugins\org.eclipse.ui.workbench\workbench.xml file, where the state of workbench when exiting is saved. This means Studio will not preload any files that were open on the last exit.
Tips for Getting Better Results from Bug and Feature Request Tickets
- Search the bug database to see if someone has already filed a similar ticket--having one ticket for a particular issue allows us to keep everyone up to date as to status and increases our engineering efficiency.
- Fill out the new ticket form with as much detail as possible: product version/build number, the operating system you're using, standalone or Eclipse plugin version (if the ticket is for Studio), did this work previously and if so when did it stop working?
- Steps to reproduce the problem. Please be as exact as possible. Code samples, screenshots and screencasts are great! We love them.
- Attach the log file if at all possible