markzhai / markzhai/AndroidPerformanceMonitor
StackSampler.doSample在部分android10机型上报native崩溃
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 6.7k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
backtrace:
#00 pc 00056cbe /apex/com.android.runtime/lib/bionic/libc.so (abort+165)
#01 pc 0037df98 /apex/com.android.runtime/lib/libart.so (_ZN3art7Runtime5AbortEPKc+1687)
#02 pc 000084c8 /system/lib/libbase.so (_ZN7android4base10LogMessageD1Ev+391)
#03 pc 003c137a /apex/com.android.runtime/lib/libart.so
#04 pc 003c0868 /apex/com.android.runtime/lib/libart.so (_ZN3art10ThreadList19SuspendThreadByPeerEP8_jobjectbNS_13SuspendReasonEPb+839)
#05 pc 003108f4 /apex/com.android.runtime/lib/libart.so
java stacktrace:
at dalvik.system.VMStack.getThreadStackTrace(VMStack.java)
at java.lang.Thread.getStackTrace(Thread.java:1720)
at com.didichuxing.alpha.lag.StackSampler.doSample(StackSampler.java:64)
at com.didichuxing.alpha.lag.AbstractSampler$1.run(AbstractSampler.java:33)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:238)
at android.os.HandlerThread.run(HandlerThread.java:67)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Android 10 native backtrace and inspect StackSampler.java at line 64, then follow the caller in AbstractSampler.java at line 33. Determine the conditions that trigger the ART abort during thread stack sampling, and validate that sampling no longer causes the reported native crash on affected Android 10 devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- mobile-dev, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100