Rubymine 5.4.3.2.1 freezes sometimes - ruby-on-rails

I am using Rubymine to work on a suite of rails projects. There are quite a bit of gems and source files, but I think rubymine should be able to handle everything despite the size...
My sources files (and gems) are shared in a Vagrant box (see https://stackoverflow.com/a/19662310/311744).
Sometimes, when I am editing, Rubymine freezes. (about 5-6 seconds).
Usually, 3-4 minutes after I restart the IDE, everything is fine. Then I have one big 5 seconds freeze, and then from that point every 15-20 seconds I have a new freeze. During a freeze, Rubymine takes 100% (or a big part) of the CPU.
I am running on MacOS 10.8.5 on a recent MBPr.
I don't want to give up Rubymine. How can I troubleshoot that ?

In case of the performance issues you should start from the troubleshooting guides on the official support site:
thread dumps
CPU snapshots
idea.log
Check that all the files are local, try to increase the heap size in case the problem is caused by the JVM garbage collection.
If nothing helps, provide all the collected data to the technical support team or to the issue tracker.
Trying RubyMine 6.0 will definitely not hurt as noted in the comment above =)
This guide is for all the users having performance issues with RubyMine or any other IntelliJ IDEA platform based IDE.

Related

Xcode builds are taking much longer than usual and causing MacBook fans to go crazy

I am building/running a relatively simple chat application. Every time I run/build the application, the fans on my MacBook get extremely loud and my computer begins to heat up very quickly. Furthermore the builds are taking a ridiculous amount of time to finish, even after editing just a single line of code.
I opened up activity monitor and noticed that "SourceKitService" was using 100% of the CPU.
Earlier today, I deleted the DerivedData folder for my project, and that still doesn't seem to solve this issue.
How can I fix this?
Try doing a deep clean (Command+Shift+K), deleting derived data, closing Xcode, and restart Mac. That usually helps me. However, when I'm running apps on my 8GB memory Mac some cause the same issue while my 16GB Mac runs them just fine.

devenv.exe hogs CPU when debugging

Short version:
When I debug ASP.NET MVC apps in VS2013 and try to edit razor views or css files, the CPU usage of devenv.exe skyrockets to the point where VS becomes unresponsive. Browser link is turned off, yet this still happens. Restarting debugging doesn't help, restarting VS doesn't help, restarting windows helps only for a short while, before the problem shows up again. How do I fix this?
Long version:
I'm having some trouble with Visual Studio 2013. Namely, after I start debugging an ASP.NET MVC app devenv.exe starts hogging CPU (to the point where Visual Studio becomes unresponsive). Some time ago this was happening only from time to time, but now it happens nearly always.
At first I thought that it was a problem with Browser Link, but the problem didn't go away after I turned it off and closing the browser while debugging doesn't have any effect.
Stopping debugging makes it stop hogging CPU, but it doesn't make the problem go away when I debug the app next time. Restarting VS doesn't help either and restarting Windows only helps for a little while.
The main clue here is that devenv.exe shows low CPU usage while VS window is not active. Switching to VS window makes devenv.exe use more CPU, but trying to do anything in VS (especially editing a razor view or css file) makes the CPU usage skyrocket.
Anyone got an idea what could be causing this problem and how to solve it?
Being unable to edit css and views while debugging is seriously lowering my productivity (the app takes good minute or two to start).
P.S. The app I'm working on right now is a nopcommerce based shop, but I had this problem before while debugging MVC apps that had nothing to do with nopcommerce.
I didn't manage to find the source of the problem, but closing all editor windows in VS seems to make it go away. If there are further lag spikes, restarting debugging might be also a good idea.
Since I didn't see this problem in a new project, it might be related to the sheer size of the solution, the number of files being opened in the editor at one time (though the problem remained even when I left one view open), the time those files where opened in the VS (I'm not entirely sure why this would be a problem, maybe it has something to do with the file history).

XCode debugging (GDB) randomly hangs while stepping through code

After running into this issue for the 10 billionth time and nearly whipping my mac air out the window in frustration, I've decided to break down and ask if anyone else has run into this...
Environment: running the latest version of XCode (as of this question: 4.2, build 4C199) for an iOS 4.2+ application (universal app).
It appears that GDB randomly decides to completely hang while stepping through lines of code. This has happened to me now on multiple codebases, and in various locations throughout each codebase. The stepping process hangs on an arbitrary point and requires that the running iOS simulator or on-device process be stopped and restarted. Typically, after restarting my debugging session I am able to get to a different arbitrary point in stepping into/thru -- sometimes even enough to actually debug my code entirely (gasp).
I tried wiping my drive, re-installing a fresh copy of Mac OS X 10.6.8 and the aforementioned XCode... No difference.
I tried switching debuggers to LLDB; this resolved the hanging issue, but I'm not as big a fan of LLDB and prefer to use my environment as close to stock as possible.
Any thoughts?
If GDB is still hanging after reinstalling your OS and your SDK, it may be a design issue with your particular code. Does this happen with other projects?
If it makes you feel any better, Apple is moving to LLDB as the stock debugger for Xcode, probably due to issues like your aforementioned issue.

Slow RVM initialization with cygwin on a 64bit machine

I am imagining that this might get me dinged for asking such a non-specific question but I'm getting desperate at this point. I'm using cygwin (I'm a bash addict) on a Windows 7 machine with huge memory and processor speed. For some reason when I do anything with RVM I get a 30 second delay before it happens. This includes but is not limited to rvm use, cding into a directory that has RVM in it and actually cding back OUT of those directories.
When this huge delay occurs I get the most insane forking of bash in my process explorer. bash processes are forked off and then disappear rapidly during the 30 seconds. I can't figure out how to really dig into this and see what is happening.
What I'm hoping someone can help me with is directing me toward resources that might address this issue (yes, I've Googled a lot and haven't found what I need--and I'm still looking) or even have had experience with this themselves.
thank you in advance and please be gentle :)
Since windows doesn't have a native equivalent of fork, cygwin must emulate it, so it will probably be a lot slower than on a real Unix OS.
See this thread:
http://cygwin.com/ml/cygwin/2008-05/msg00360.html
Also at least one person has reported that forking on cygwin 1.7 is slower than 1.5:
http://cygwin.com/ml/cygwin/2010-09/msg00871.html
Does your development require Windows, or can you do your work in a VM instead?
Does it work in Windows?
According to the FAQ, rvm is not intended to work on Windows.
You should use pik to get similar behaviour in Windows (although it misses the gemsets, it allows you to switch between ruby-versions, and with pik each rubyversion has its own set of gems).

application wont start or load in blackberry simulator

I'm developing an application on two different machines (home and work) and while the home one seems to run just fine, the work one is, for lack of a better word, possessed. It has been exhibiting the following issues:
When loading the application, it will start at the simulator's main screen instead of starting the application at random intervals. You can start the application and have it work fine, then close the simulator, reload, and have the same codebase not load.
Going to applications doesn't show the application itself, in fact it never does.
Trying to load the applications cod file (File->load java program) never works. Tried the steps in this thread, with unreliable results.
Extremely small changes, such as modifying the value of a width variable by one, commenting out a function such as makeMenu or adding a button will cause code to no longer work, with no errors shown by the IDE.
Using clear.bat with sometimes work, sometimes not. Same with manually removing all files with the name of the project.
reinstalling the eclipse environment and the blackberry plugin did nothing more then burn off an hour.
having "load on startup" in the blackberry_app_descriptor.xml file is set.
Both systems are using Eclipse 3.5.1, BB plugin for eclipse 1.1 beta, Java 4.5 with the 8300 simulator. THe only difference that I am seeing is the operating system between the two systems. The work one being XP Sp3, home being vista. THe vista one isn't perfect, but I can test variable changes without flipping a coin to see if the app will even load or not.
I've tried the solutions that were similar on this forum, such as this one, but it looked to be that those solutions are dated as none of the options for the steps existed in my eclipse install.
So has anyone ran into such baffling behavior, and can it be fixed? Anything that I might have missed that could be tried?
I've been seeing this behavior with the new 1.1 plugin, the application doesn't load on startup and the FIle->load java program doesn't help. For me, the solution was I have to run a clean build every time, that is the eclipse clean and build instead of just build, not the clean.bat... Hope this helps!
Try clearing resources that have improper naming structure in your projects stuff with spaces or special character in the name of the file.
It took me two days to figure out.
One solution i got regarding your problem.
As I See Please run the application first time as Run as blackberry simulator
that is got start and here pick up run and then Run as Blackberry simulator

Resources