There are multiple Chromium Helper processes in my system. They eat up lots of resource and slow my MacBook significantly. So far I only know they are related to android studio and flutter application development.
I don't know what I've done so these process start to emerge. Can anyone tell me what do they do and how to turn them off?
Related
Is it possible to use AndroidStudio (for Dart) withOUT running an emulator?
Context: I am a complete newbie and have started reading some intro books and following online tutorials. I am aiming to learn DART and FLUTTER and have successfully installed AndroidStudio and an emulator and ran some successful test projects like helloworld.
The thing is, these early example projects are VERY basic things, to teaches me about variables and syntax etc and outputs results to the console. At this point, i do not need to boot up an entire emulator (which adds a layer of clunkiness when running)... but AndroidStudio seems to insist on one being activated?
I could use "DartPad" (which i love) for simple stuff - but it's limited and i'd prefer to learn one dedicated IDE if possible.
It depends on what you are actually running. If you are using Dart alone, you should be able to run it. Personally, I do these kinds of projects within IntelliJ Idea - which Android Studio is based on anyway, but doesn't come with the Android "overhead". Microsoft Visual Studio Code is another valid option that many people use.
If your project is based on Flutter (i.e. it contains UI), you need a "device" to run on - it might be the Android emulator, iOS simulator, Chrome or native (experimental).
I have a very big problem using Android Studio.
Every time I make a code changing, I have to check if all has gone well launching my app; but as soon as I click the "Run app" or the "Apply changes", it's the end: it starts the Gradle build process, which take even 30 minutes to complete, and furthermore Android Studio take the full control of my computer, not allowing to do nothing anymore (like open the browser, open notepad++, and so on...).
Can anyone help me?
Thanks
If you use Eclipse you won't have this problem anymore. but if you want to stick with android studio and gradle you can run your emulator and gradle once and whenever you want to compile your code run it on the already built gradle. this means that do not close the emulator and run your program on it again and again. this way you will not have to spent alot of time on loading the emulator and gradle
Android Studio is not a very light software.It uses a lot of your system RAM and CPU power.So if you are using an old system then it is obvious that android studio will run slow.If possible then upgrade your system.
And one more thing it's better to use actual device rather than Virtual Emulator for our application working test.
I've searched all over the web for the past 3 days and can't seem to find a solution. I've done everything mentioned in this post:
Android emulator not showing in Visual Studio
It seems all the 'working' solutions to this problem has been stated in what this guy says he did in his original post, including restarting ADB server (kill and start), restarting my computer, reinstalling emulator and HAMX, installing and running as an admin, changing the timeout delay, reinstalling almost everything, making sure my emulator is installed, etc.
It keeps saying Gradle build finished in 475ms, etc and then waiting for target device to come online for like 5-10 minutes and nothing happens. No emulator shows up. I can't seem to find the solution to this and I am on the verge of giving up, I really need Android Studio to work so I can start on my app.
Can I please get some guidance with this?
If it's relevant, I'm using a Mac.
Have you tried this. Go to the emulator settings and set the Graphics Emulation mode to Software GLES. The default mode will be automatic. I am not sure how it works, but that worked for me on two Linux machines. Being software emulation, the performance of the emulator will not be as good as when using hardware graphics. It seems to be a bug with the SDK.
For me the only thing that worked in macos was to disable docker before starting Studio.
Wipe the data of your Android virtual Device and then start the emulator.
I was using Android studio 4.2 and faced this issue.
No Solutions worked for me so I just erased android studio files. Updated to Android Studio Arctic Fox.
Link to remove android studio files from mac : How to completely uninstall Android Studio on Mac?
For Windows : How to completely uninstall Android Studio from windows(v10)?
It is some time now since I first heard about instant run in Android Studio 2.0. Is it ever coming to IntelliJ Idea? I have 2016.1.2 and still nothing. I can imagine it can speed up development. I am still tearing my hair every time I press run...
Couldn't find any valuable information about this online. All what google finds is just "IntelliJ and Android Studio is made on the same code base" I guess it is more complicated than that.
Seems like it's going to be released in Intellij 2016.2
Quoting 2016.2 EAP Release Notes:
Android
Android Studio 2.0 features.
Edit:
Looks like it was eventually released and made production ready in Intellij 2017.1
Quoting the What's New page:
Instant run
This release adds many stability and reliability improvements to
Instant Run. If you have previously disabled Instant Run, the Android
team encourages you to re-enable it.
No. From IntelliJ IDEA 2016.2 Notes:
Android
The update includes the Android Studio 2.0 features: faster Emulator, experiment GPU Debugger, faster full builds, and code generation and testing for App Indexing. Note, Instant Run is not fully-merged yet.
Running Android Studio 1.0.2 for Windows
Using a new Blank Activity or Blank Activity with Fragment project (bug happens with both). Haven't modified anything in the code yet. Using API 10: Android 2.3.3
Often immediately, sometimes shortly after I drag or edit my first/any UI element into activity_main.xml, Android Studio freezes and I have to close the process in task manager to get it to close.
I notice that in Task Manager the Android Studio Windows Launcher is taking about 25-30% of my CPU while its frozen.
What's going on here? Any ideas?
....
I may have found a solution for this.
I theorized that perhaps it was just the windows display that was frozen (the visual rendering of the Android Studio program itself) and guessed that perhaps this was using a DirectX device to do the rendering of the Android UI.
I happen to have another app running on my computer that uses a DirectX device for rendering (SimpleJungleTimer, an app I programmed with a DirectX overlay for League of Legends jungle timers). After I shut down this app Android Studio appears to be working properly (not freezing when working with the UI anymore)
Ultimately it sounds like this is a bug with Android Studio itself where they don't properly kill / reload the DirectX rendering device when it is in conflict with another app's active DirectX device (something that the android studio developers should probably fix), however until the android studio developers fix this you should be able to get around this bug by making sure any other applications that might use DirectX for rendering are shut down while coding in Android Studio so that their DirectX rendering devices don't conflict with Android Studio's DirectX device.