I love Aptana, but sadly it crashes on me almost every day. I'm stubbornly sticking with the editor, but if I can find and fix the instability, I will have no major complaints with it.
I'm running Aptana Studio 3, build: 3.0.9.201202141038 but the crashing has been ongoing ever since I installed Aptana 3 many months and many version upgrades ago. Following the most recent crash I checked the Aptana .log but there was nothing valuable in there. There was however quite a bit of info in the OS-X "view details" notification following the crash: http://pastebin.com/02JrqrUQ
Sometimes it crashes following SVN actions, but also, as most recently, it will crash when it's just sitting there.
I'd appreciate any suggestions on how I can address this issue. I believe that I previously
had tried a reinstall which didn't fix the issue, but if no one has anything else to try, I guess I may give that a try again.
Thanks,
Dan
---- UPDATE ---
Ingo, Thanks for the response. That thread on appcelerator.org definitely describes the errors I was seeing.
Following your advice, I upgraded to the Aptana nightlies (now on version 3.1.0) and have not seen a crash in 2 full days. Hopefully any future crashes will now be few and far between and no longer a daily occurence.
Thanks so much for the response.
Thank you very much for your information. We've been tracking this issue, but honestly, it's been a bear to diagnose and reproduce, since most of the references don't point to any code of Studio--only the underlying versions:
https://jira.appcelerator.org/browse/APSTUD-3682
Please follow along on the linked ticket for more information. You might try the latest nightly (3.1 version) at preview.appcelerator.com which is built on top of Eclipse 3.7.
I had this same issue - and then I could not even open Aptana. Right click on the program -> click Properties -> Compatibility (Windows 7) > and tick "Run this program as an administrator"
This worked for me temporarily - the real fix is to delete or rename the .log file in your workspace.
Related
I have a radio button that is represented as a pbdatawindow, when I run setcelldata to pick an option it works fine on my laptop but fails on my colleagues laptop. If we try the run the command again on my colleagues laptop we get a fatal error from UFT.
The only difference between my UFT install and my colleagues is that my colleagues version is installed in French. Has anyone seen a similar issue?
PbWindow().PbDataWindow().SetCellData 1,1,""
Few things to try:
What version of uft are you using? - perhaps check for newer of see if there is a patch available?
Jump onto the microfocus knowledge base and see if there is anything around power builder.
You say the machines are the same but does that include every application too? In the past I've known that if you install applications after uft it can break its references. Try uninstalling and reinstalling uft. There is a repair option but uninstall/reinstall is normally more thorough.
Try and clear out all your temp and user settings.
In your user profile backup then remove all folders with mercury, hp, Hewlett-Packard and microfocus.
-The go to %temp% and clear evetything.
Try and pin down the problem - Has your colleague tried the English version or uft? - if that works, is it an option? (everyone use the same version)
If it doesn't work it suggests it's your colleague's machine as opposed to uft.
Is evetything such as the resolution and browser/application versions the same? Or simply try another French localised machine?
What's the fatal error? Does it provide any clues on why it failed?
Finally, You're paying a lot for commercial software. Don't suffer in silence :-)
Log a support call with microfocus. It's a bit long winded but Back in the day they used to be pretty good at helping. They'll ask you for logs and knowing how to get that is good to know.
There's more to try - let me know how you get on.
While developing a Cocoa sandboxed application, I discovered that if I switched it to non sandboxed, in all the Open Panels of the application, the right click commands (Duplicate, move to trash etc.) do not work any more. I am certain they did work no more than two weeks ago, but I have reverted the project to old commits and the misbehaviour is still there. I tried everything, until I realised that this misbehaviour now appears in all my projects, if I switch them to non-sandboxed. This makes me think it may be some kind of bug introduced in 10.14.2 or something similar. I hope somebody else has experienced the same issue so that we can understand better what is going on. Thanks
P.S. I am using the latest Xcode 10.1 (10B61) and tried on several machines. It is the same misbehaviour.
The OS might be confused by having some contradicting leftover knowledge about sandboxed and non-sandboxed versions of the app with the same version / bundle ID / signature.
Some things to try:
Test the app on a fresh user account.
Delete the app sandbox container from your Home Folder > Library > Containers.
Temporarily change app bundle ID to something new to see if it’s still affected.
I'm following the instructions here but it seems not to work. I'll contact the developer, but wonder if someone has been able to make it work somehow.
The installation process is completed, but Netbeans doesn't see the plug-in. I assume it is deployed incorrectly.
Not sure how it got fixed but suddenly upon starting the IDE an update for the plugin showed up and it started working afterwards.
I.T. gave me an upgrade to V5 and I can't see my directory listing.
Maybe I bumped a hotkey i don;t know about?
You can see a screengrab here http://dl.dropbox.com/u/23768853/help.jpg
I'm combing thru all the preferences but so far nothing, anyone know how to make it come back?
Fixed !
I.T. re-copied the application into the application folder and webstorm is working normally again.
Surprising to think that the application can run even after a corrupt install.
I am experiencing an error when running my project in xcode4.
A couple of times it stopped when it was trying to copy the database to the build directory, telling me the sqlite-file isn't there. After restarting my Mac it now stops in the build process. The text above the info-progress bar tells me "attaching to [project]".
This doesnt happen when running my project with Xcode 3.2.6.
Does anybody know a workaround for this?
Thank you very much in advance.
best regards
Tom
Apparently Xcode is a bit more serious about what's really within the xcode-project, not just laying in the directory. The error means I forgot to add the file in the directory to the project again after I mucked around with it.
Now that the file was added to the project everything is working again.
I hope it saves a bit of time in case somebody else comes accross the same problem.