The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I never saw VS consuming CPU cycles just by being started, if I do not request it to perform some operation.
Plain editing (with IntelliSense support and immediate marking of syntax errors) is barely noticable on the CPU load. If I start the program I am developing to run under control of VS, there is of course some CPU load even when the program is at a breakpoint or waiting for input, with no active threads. This is to be expeced: VS monitors e.g. the heap and GC continously. But this is at such a level that I never though of it - nowhere close to 20%.
If you have threads running under the debugger, and these are in some active state, you must expect the CPU load to be somewhat higher than if you run the executable standalone, especially if you set a lot of conditional breakpoints, and those threads hit the breakpoint without satisfying the condition. Other debugging functions, like monitoring memory use etc., are also bound to take some resources.
So I cannot agree with your statement.
(For the sake of being impolite: But on the other hand, I have been using Eclipse...)
I've seen this same issue with Arduino studio (it's written in Java) and I have to shut down the IDE all the time or the fans will run on my PC as the CPU usage goes way up.
Maybe Android Studio was checking for SDK updates or other types of updates. Or maybe Gradle (build system) is running in background?
Maybe it was still doing some background updating since you just installed it? Is it keeping high CPU now?
I haven't seen Android Studio be that bad and I do quite a bit of Android development. Every revision of Android Studio does get a bit more bloated however.
I Opened Android Studio and Watched Task Manager
I have the latest version Android Studio and I fired it up and it is sitting on the splash / open a project screen at about 0.8%. Then I opened a project and let it sit and it's at 0% while I'm doing nothing in it.
It was a background worker (I left it run overnight to finish) that installed a local copy of Gradle, even I have the latest already installed on shared location... After finishing it, it came to peace with the computer...
Wondering why the shared Gradle didn't satisfied it, maybe that I installed it under /opt...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
It was a background worker (I left it run overnight to finish) that installed a local copy of Gradle
Interesting. It is a bit disconcerting that it does this stuff in the background but doesn't even let you know so we see the behavior and can't really tell what is happening. It's not very helpful of the devs to not just give a warning that the background thing is running. Glad you discovered what it was.
I'm guessing it is the IntelliJ-based Android Studio we're talking about. IntelliJ is notorious for its long indexing times :P
The JVM is - in my experience, at least - not too CPU-intensive, it is mostly the RAM that gets used up quick (or at least with the ConcMarkSweep GC; in Java 8, the G1 seems to do better: -XX:+UseG1GC)
I got a new coffee mug for Christmas! To be fair, it is actually a self-heating mug that lasts around 2.5 hours on a charge and keeps my java nice and hot. Out of the box, it's supposed to maintain 130F but the temp can be adjusted using an app that I couldn't get to install on my Kindle Fire...I guess I can live with the default.
So this got me wondering why the manufacturer chose not to offer a Windows based application? I think it's be great to control my coffee mug from my desktop or Windows Phone!
Another noteworthy gift from my wife: concert tickets to see Dream Theater in Chicago in a few months!
I find it both ironic and humorous that you can't install that app on your Kindle Fire.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
so you make your coffee, and realise you forgot to charge the cup.
...anyway I'd never take that long to drink a cup of coffee, unless I fall asleep half way through (which does happen once in a while and no, it's never decaf), in which case I make a fresh one.
(In fact anything over 10 mins (very rare) is pour out and make another, I can't abide stale coffee.)
The Visual Basic mug was the second most popular and the C# mug came in third-place this year. Unfortunately the C++ mug came in last place again signaling the decline of this once popular programming utility.
I thought about getting one of these for my wife to keep her tea warm due to this thread. I found it on Amazon and everything looks great until you read the reviews. Three things keep popping up. Delamination occurs after a few weeks, the springs in the charger contacts fail causing the charger to no longer work, and the app is buggy causing it not to work on Android devices.