markzhai / markzhai/AndroidPerformanceMonitor
LooperMonitor中println方法处理是不是有问题？
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 6.7k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
看Looper的代码，println在开始和结束都会触发。那这里println方法里面的逻辑是不是存在问题？个人感觉第一次调用println方法的时候应该忽略，不做处理；从第二次调用开始计时才是正确的。因为第一次调用是在某个消息处理结束之后触发的，第二次调用才是对应真正的后续消息开始处理的时间点。
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 at the LooperMonitor println entry point and read the Android Looper message-dispatch sequence it observes. Trace which println call follows a completed message and which precedes the next one, then verify whether timing begins at the intended call; the issue is done when that behavior is confirmed and covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100