Status Update
Comments
co...@protonmail.com <co...@protonmail.com> #2
rm...@google.com <rm...@google.com> #3
Please restart the device and check for this issue on the latest software build. If the issue is still reproducible please share the bugreport(to be captured immediately after resolving the issue) and screenrecord of the issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen Record of the Issue Please capture screen record or video of the issue using following steps: adb shell screenrecord /sdcard/video.mp4 Subsequently use following command to pull the recorded file: adb pull /sdcard/video.mp4 Attach the file to this issue.
vs...@google.com <vs...@google.com> #4
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
This bug persists with the latest build
Debugging information
Google Play services
com.google.android.gms
Version 225014044 (22.50.14 (190400-499278674))
System App (Updated)
Android System WebView
com.google.android.webview
Version 541408544 (109.0.5414.85)
System App (Updated)
Network operator: Fido
SIM operator: Fido
Filed by Android Beta Feedback. Version (Updated): 2.31-betterbug.external_20221207_RC04
To learn more about our feedback process, please visit
[Deleted User] <[Deleted User]> #5
[Deleted User] <[Deleted User]> #6
Please restart the device and check if the issue persists?
co...@protonmail.com <co...@protonmail.com> #7
co...@protonmail.com <co...@protonmail.com> #8
The issue has been fixed and it will be available in a future build.Please refer the release notes link
tn...@google.com <tn...@google.com> #9
More details in
co...@protonmail.com <co...@protonmail.com> #10
"Hey on your dev machine, you probably want to tweak these settings if you've got a bunch of RAM (like 32GB or more)" and then list a breakdown of each thing.
I have a feeling that my 64GB machine that basically runs studio and chrome could probably be tweaked to perform better than just increasing studio from 1024 to 4GB or something.
I think I said this before but it seems like it would maybe make the most sense to just have a doc describing "potential" tweaks on high end machines. From ram to different java args or gradle args or sharing gradle instances and all of that good stuff.
uc...@google.com <uc...@google.com>
xa...@google.com <xa...@google.com> #11
Jon/Neal, lets sync on this next week and come up with a list. It's true that this is potentially complicated with the RAM setting for Studio, Gradle, Kotlin compiler daemon, Javac daemon, and potentially more as we start using out of process tasks execution for things like lint/R8.
jo...@google.com <jo...@google.com>
co...@protonmail.com <co...@protonmail.com> #12
@ Xav, any movement on this by chance?
"It's true that this is potentially complicated with the RAM setting for Studio, Gradle, Kotlin compiler daemon, Javac daemon, and potentially more as we start using out of process tasks execution for things like lint/R8."
Description
"Is there a list of like all of the ram settings to increase if I have like 64GB of ram on my machine. Currently all I do is eidt Custom VM Properties and I give it like 16GB of ram. Are there other ram properties I can increase for gradle or anything like that? I literally bought this computer with 64gb of ram so that i can have slack, chrome and android studio running as smoothly as possible. I don't do anything else besides that on this work machine."
"That seems like something we should document properly on
My simplistic view on this is that you should set your Xmx setting to 2g to 12g for Studio depending on your project size (too much heap is not always great either). Then you should increase the Gradle daemon heap size as well.
Other than that, use a Linux machine with an SSD if possible, and only use the emulator if you have RAM and CPU to spare. Recently, I've heard that there is a separate Kotlin daemon, and who knows what is going on with all the annotation processors in use, so it is better if the build team chimes in on the rest of the settings.
Please link to the bug here in case you do file it." -vsiva
TL;DR
I bought a Mac machine with 64GB of ram. All I ever use is chrome, AS, and slack as this is strictly a work machine. I still have perf issues with AS and I just want a quick reference to all of the values that I should increase from their defaults to take advantage of this custom machine. It'd be GREAT to also identify the point of no return/value (no point of increasing X past Y-GB or something like that)
Thank you!