Assigned
Status Update
Comments
sg...@google.com <sg...@google.com> #2
I just attached a minimal test application with duplicated and multiline traces. Provided are a couple of logcat files and screenshots.
To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1. The new way results more time-consuming to me while debugging and reviewing the logs.
Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)
To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1. The new way results more time-consuming to me while debugging and reviewing the logs.
Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)
to...@gmail.com <to...@gmail.com> #3
I have the same problem.
to...@gmail.com <to...@gmail.com> #4
I also have the same problem.
ri...@google.com <ri...@google.com> #5
I also have the same problem.
to...@gmail.com <to...@gmail.com> #6
I also have the same problem.
sg...@google.com <sg...@google.com> #7
I also have the same problem.
to...@gmail.com <to...@gmail.com> #8
Was it fixed reverting to the old behavior, or was it fixed making the deduplication configurable?
What release version will include the fix?
What release version will include the fix?
ri...@google.com <ri...@google.com> #9
I still have the same problem on my version.
Android Studio 3.1.1
Build #AI-173.4697961, built on April 4, 2018
JRE: 1.8.0_152-release-1024-b02 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 8.1 6.3
Screenshot attached.
Is there any way to customize this kind of behavior?
Android Studio 3.1.1
Build #AI-173.4697961, built on April 4, 2018
JRE: 1.8.0_152-release-1024-b02 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 8.1 6.3
Screenshot attached.
Is there any way to customize this kind of behavior?
sg...@google.com <sg...@google.com> #10
@jose.aladro.jsc@gmail.com This change in behavior was inadvertent and I reverted it. The fix will go out in 3.2.
to...@gmail.com <to...@gmail.com> #11
how long before 3.2 is released? or should we just go back to 3.0 while we wait?
to...@gmail.com <to...@gmail.com> #12
The fix will go out in 3.2 Canary 13 (we're at 11 now). If you're willing to put up with some instability use the canaries. I can't comment on when future stable versions will land.
Description
I've seen some other issues reported here regarding CI and memory issues but I think this is a little different as in my case this does not happen in CI and is 100% reproducible.
This only started to happen recently but unfortunately not sure if it's 100% related to R8 8.10-dev and not sure what to provide since the task never ends to generate a dump (Or at least I did not wait long enough).
My build command for releases is:
Before it always worked normally, now the first run after code change will have the R8 task hang. Pressing ctrl+C to kill it and restart the exact same script just after will always then work and the R8 tasks run in 2 minutes as usual.
This is 100% reproducible I suppose there's a way to debug this.
Note: The command in CI is using --no-daemon and -no-configuration-cache but in theory since the script have the stop it should behave mostly the same.