I am running Apache Spark in IntelliJ, using the console to send requests to my application.
I have noticed something I find quite strange. On my Mac, when running my program and having IntelliJ as the selected window i.e. full screen and visible; I get through 1000 iterations in ~5 minutes. When I start the application in IntelliJ and then make the visible screen another application, but do nothing with it - literally just leave the Mac alone, when I go back to the Scala Console after ~5 minutes it has only performed 300 iterations! Similarly, if the app starts and then the screens turns off (but my Mac doesn't sleep - I made sure of that) I get the same issue: only 300 iterations.
Is there any explanation for this?
Related
I'm a seasoned software engineer and have used eclipse for well over 10 years. In the last week, Eclipse has decided to rebel against me. I'm dumbfounded.
Problem: I'm getting periods of very long UI unresponsiveness - on the order of 3 to 10 seconds. Generally, I'll be typing when the UI just stops writing text. It can vary from displaying spinning circle to not rendering anything in the window. Workspace building also slows down significantly.
I'm pulling my hair out trying to get tasks done! Any help appreciated.
Details:
It appears to start 10 minutes or more after starting eclipse. If I restart, it'll be ok for a few minutes.
This can happen in during any text entry. Though it's especially bad on code completion cases (i.e. "dot, cmd+space). Eclipse can also become unresponsive during anything else (moving the cursor, changing tabs, scrolling, etc).
CPU is not maxed out, though it appears CPU is pretty consistently at or over 50% - so maybe eclipse as pegged one thread/core?
Things I've Tried:
Updated from Neon.3 to Oyxgen.2. Deleted all projects from workspace and reimported. Upgraded memory in ini to -Xms512m -Xmx4000m -XX:PermSize=256m
-XX:MaxPermSize=512m. Deleted some metadata from a eclipse resource dir (don't recall which). Updated Java. No change. Haven't tried uninstalling all eclipse and reinstalling yet.
Setup:
Windows 10 Home (up-to-date), 12GB RAM, 64 bit, Oxygen.2 (4.7.2)
How large is your project? Do you build using Eclipse, or do you build externally?
If you notice a progress bar in the lower right side of the GUI during these periods of unresponsiveness, it's likely Eclipse's Build Automatically feature causing your issue. If so, it can be disabled under Project -> Build Automatically.
I have a large (> 25k) app that I've been developing in Scala/Akka/Play for a couple of years now. I'm in the process of upgrading it to the current version of the world (everything was a major version or two behind), which means getting it running in Activator. I'm gradually wrestling my way through that, but I'm somewhat stymied by the fact that Activator's "compile" window is very short -- only a few screens long -- so most of my 50-some-odd remaining compile errors are scrolling off the top. I'd really like to be able to read the entire thing, since I assume that most of these are knock-on errors, and only a few are really significant.
Where does the actual compile log go? How can I get to the whole thing?
It sounds like you're trying to use the UI mode when you were happy with the command line mode in Play 2.2; the command line mode is still there, see http://typesafe.com/blog/typesafe-activator---an-update-and-roadmap-preview for some background. Just run "activator" instead of "activator ui". The UI mode is not something that's "production hardened" yet, it is primarily intended for tutorials (though we are working to change that).
That said the compile log should not be truncated in the UI and we appreciate bug reports at https://github.com/typesafehub/activator/issues including one about this truncation.
I am trying to run my projects in Eclipse, whenever I used to run any program a window appear and it shows that project is launching and building.
This never happened before. In fact, it was working very okay an hour before but now, even for old created project it showing this and not moving ahead.
Is this a general thing happened in eclipse as I haven't seen this before.
I want to get out of this to move ahead and to run the project.
The Launcher looks like this :
The progress Bar is also not moving ahead if it's building the project.
It's definitely normal to see; there's times I'll see it two or three times in a day. It shows up if the launching process is waiting on anything or is expected to take more than a couple seconds.
In your case, it seems to be stuck on "Building workspace," which happens when you open Eclipse. The more projects you have in Eclipse and the more sections of workspace you have (groups of tabs), the longer it takes to build your workspace. So I'm going to wager a guess that you tried to launch a project within the first minute or two of Eclipse being open. Am I right?
If that's the case, just wait a bit, and watch the lower right corner (where it says "Launching Clock" in your screenshot). When it shows it's stopped trying to do start-up tasks, you should be good to go.
If Eclsipse had been open for a while, then perhaps Eclipse is busy with other junk and calling it "Building workspace." Maybe it's having a hard time understanding what to do with one of your projects, so check for compiler errors. You can also try to "clean" your projects (Project -> Clean).
If that also fails...hmmm...I'm sure there's other options before you get to this point, but you might need to re-install Eclipse. I suppose there's a chance that in the deep dark corners of Eclipse, a file was corrupted, causing Eclipse to hang on a task that requires a missing/bad file. But before you go this far, make you get second or third opinions, because I might be missing some simpler cause of your Eclipse hanging than what I've listed already.
I found the solution.
I don't know what was the error and why it was displaying the Launcher window and stuck there. But, I forcefully stopped eclipse using Task Manager and then restarted it.
When restarted it took few minutes (more than usual time) and I was done with it. now it's working okay.
Re-installation of Eclipse also worked but i tried this before re-installing or upgrading.
When I enter a hotkey [any hotkey], AutoHotKey doesn't respond. However, it will respond if I edit, save, and reload it. After which, it will respond three or four times then I must go through the same process of editing, saving, and reloading it again.
I have uninstalled and reinstalled the program 10 or more times.
Before it began to not respond, it would leave a space after each string. [I'm not sure if that is related to my problem or not.]
I am using Windows 7 and IE 10. I reinstalled IE 8 and IE 9 to see if either would correct the problem. The problem remained.
Thanks for whatever help you may provide.
Me too
I have encountered this same type of problem. AutoHotKey loads my script and responds for a while, then after X number of times the script simply stops responding.
Resolution
To resolve these types of problems I found that opening the debug screen (double click the AutoHotKey icon in the task bar) generally shows that my script is busy running, and doing something. From there it's a simple matter to identify why it's still running.
Since the script is currently busy satisfying a previous request, then a new request can not be initiated.
In my case the problem is some runaway loop that is processing more data than I had expected or it's stuck in some infinite loop.
If you leave the script running while it's stuck, you might also want to open the task manager to see if it's consuming any CPU time or if it's gradually eating more and more memory.
I am using Eclipse for Java development. I have a number of plugins (Maven, Subversive, JBoss reverse Engineering tools, etc), and the system seems to hang fairly consistently, to the point where it can be 10-20 seconds from a mouse click until it responds. I have given it a gig of memory in the configuration, and it is not even using half of that. When it hangs, it completely pegs one of the processors, and I see large numbers of Page File Deltas.
Is there any way to see what is happening inside Eclipse? Which plugin could be causing the problem?
I believe (although I am not positive) I am running Eclipse 3.5.2. I am running on Windows XP, SP 2 or 3 (I do not manage the machine, my company does, so I am not positive how up to date it is).
First, the one plugin that can help investigation this would be MAT (Memory Analyzer).
Full tutorial at Vogella.
Second, make sure to use an optimized eclipse.ini launched with the latest JDK (6u22) and check if the issue persists then.