Aptana sometimes freezes on Mac OSX after changing workspace

Question

I love Aptana and use it heavily, but I have had strange and annoying problems - from time to time, the Aptana process freezes in the background and I can’t start it or kill the process - the only solution I found is to restart my Mac. I am using a MacBook Pro with Mavericks on it and I have the latest version of Aptana. I also use the SVN plugin created for Eclipse Studio. The first symptom I have is another Aptana icon that appears on my dock bar, one is constantly there, and suddenly another one appears - I think this happens when the workspace changes. I can no longer switch to Aptana using the original icon, I have to use the one that appeared later. After I left the Aptana instance represented by the new icon, I can no longer activate it, and I have an Aptana process that I cannot kill, and it will not be displayed if I find ps -A in the terminal.

If anyone knows how this happens, I would like to avoid it - just don’t tell me not to switch my workspaces, because I am dependent on it - I am a professional web developer working for several companies and Workspaces are a way of organizing my work.

If someone knows how to kill this aptana instance, this will also be a temporary solution - killing him from the Activity or Force Quitting monitor will not help, I just get a warning that I will "lose unsaved changes", but after I click on Force Quit, nothing happens - the process still exists.

And yes, this does not happen with any other application on my mac - thanks for the question: D

Thanks Victor

Answer 1

For those who may encounter this problem - this is what happened at the end. I accidentally found out that if I close Chrome, there is also an instance of Aptana, and I can start it again. So try closing Chrome, and the problem can be resolved. This applies to Aptana Studio 3.4.2.201308081805 - I have yet to install the latest version, but it can be the same thing.

I am wondering if this has something to do with Java? The only thing I see in general

Answer 2

Here is an easy way to kill him:

$ ps -ef | grep Aptana 

then kill the process

 $ kill -9 <PID> 

replace actual process id

hope this helps.

Answer 3

This is a bug, and according to https://jira.appcelerator.org/browse/APSTUD-8275 it will be fixed in version 3.6.1.

Answer 4

Aptana bug tracking notes this as fixed for release 3.6.1: https://jira.appcelerator.org/browse/APSTUD-8264 However, in August it was marked as fixed, and the most recent release available for download is still equal 3.6.0 (Anyone with Aptana have an idea when a fix will be released?)