Status Update
No update yet.
Comments
da...@google.com
Which Android build are you using? (e.g. TQ3A.230705.001.A1)
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
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.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
se...@google.com
We can't repro the issue on our test devices so can't really help with the build number and the bug report unfortunately we got this crashes through our crash reporting service. I can share a list of devices and os versions this crash is occurring if it helps.
ti...@gmail.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
se...@google.com
se...@google.com
We've resolved this bug, and the fix will be included in the upcoming version. We'll update this issue once that version is released.
ti...@gmail.com
ti...@gmail.com
following is the crashlog recently we are facing
build.gradle:
implementation("com.google.android.play:review:2.0.2")
implementation("com.google.android.play:review-ktx:2.0.2")
Exception:
Log1:
Fatal Exception: java.lang.NoClassDefFoundError
Failed resolution of: Lcom/google/android/play/core/common/PlayCoreDialogWrapperActivity;
Log2:
Caused by java.lang.ClassNotFoundException
com.google.android.play.core.common.PlayCoreDialogWrapperActivity
com.google.android.play.core.review.zzd.launchReviewFlow (com.google.android.play:review@@2.0.2:2)
com.bnb.paynearby.legacy.PlayStoreInAppFeedback.showInAppPopupFeedback$lambda$1 (PlayStoreInAppFeedback.java:34)
com.google.android.gms.tasks.zzi.run (com.google.android.gms:play-services-tasks@@18.1.0:1)
android.os.Handler.handleCallback (Handler.java:958)
android.os.Handler.dispatchMessage (Handler.java:99)
android.os.Looper.loopOnce (Looper.java:257)
android.os.Looper.loop (Looper.java:368)
android.app.ActivityThread.main (ActivityThread.java:8839)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:572)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1049)
se...@google.com
I looked at that it is my horrible implementation in Exit / Entry Hooks with getting method name via stacktraces. It is not to hard to provide better implementation, just need to pass this info from dexter.
al...@google.com
If you want something really quick the JVMTI StackTracing functions are actually pretty well optimized for just getting the immediate caller. Changing you onEntry function to call back into JNI to use that would be pretty easy and only cost a JNI transition.
se...@google.com
Performance was improved by:
- making entry / exit hooks better
- remove instrumentation from sqlite's hot path
Description
From
Having the same problem on ArcticFox :
Android Studio Arctic Fox | 2020.3.1 Canary 6 Build #AI-203.6682.168.2031.7132434, built on February 8, 2021 Runtime version: 11.0.8+10-b944.6842174 x86_64 VM: OpenJDK 64-Bit Server VM by N/A macOS 10.16 GC: G1 Young Generation, G1 Old Generation Memory: 4096M Cores: 12 Registry: external.system.auto.import.disabled=true, debugger.watches.in.variables=false Non-Bundled Plugins: Dart, org.intellij.plugins.markdown
DB with around 1000 entries on two tables, when running a join query, query takes around 1-3 seconds to execute, when inspection is disabled it doesn't go above 40ms. Could be a good idea to display a warning message when inspector is started ? I can try to build a sample project to see if I can reproduce.