Status Update
Comments
bk...@gmail.com <bk...@gmail.com> #2
Hi, any updates on this issue?
dv...@gmail.com <dv...@gmail.com> #3
no, just modify the code by yourself. I have fix that.
If you want to fix this by yourself, following the instructions in this document. you can use wsl in windows to download and compile the following source code.
or, you can use the AARs compiled by me. you need download the AARs, and refers in the build.gradle files.
// benchmark-macro use wireEnum
implementation("com.squareup.wire:wire-runtime:4.9.3")
// load androidx benchmark macro junit
// use MacrobenchmarkRule
implementation(files(localProperties.getProperty("benchmark-macro-junit4.file")))
// load androidx benchmark macro
// use CompilationMode,StartupMode
implementation(files(localProperties.getProperty("benchmark-macro.file")))
// load androidx benchmark common
//use Arguments
implementation(files(localProperties.getProperty("benchmark-common.file")))
and you should define path in local.properties, like this(you may need change the path , depends on where you save your files.
benchmark-common.file=..\\aar\\benchmark-common-release.aar
benchmark-macro-junit4.file=..\\aar\\benchmark-macro-junit4-release.aar
benchmark-macro.file=..\\aar\\benchmark-macro-release.aar
ap...@google.com <ap...@google.com> #4
Branch: androidx-main
commit ec13e616312e4026429dfa6a86b820725f30e2be
Author: Chris Craik <ccraik@google.com>
Date: Wed Dec 06 09:59:35 2023
Fix FrameId parsing in FrameTimingMetric
Fixes: 303823815
Bug: 306235276
Test: SliceTest
Test: FrameTimingQueryTest
Relnote: "Fixed crash in FrameTimingMetric failing to parse frame id,
especially on certain OEM devices."
Change-Id: Ia24bc3c90b317252f579cc2425547f034ef96ef8
A benchmark/benchmark-macro/src/androidTest/java/androidx/benchmark/perfetto/SliceTest.kt
M benchmark/benchmark-macro/src/main/java/androidx/benchmark/macro/perfetto/FrameTimingQuery.kt
M benchmark/benchmark-macro/src/main/java/androidx/benchmark/perfetto/Slice.kt
cc...@google.com <cc...@google.com> #5
The above fix should address the issue, and you can confirm it does with a snapshot build 11193231 or higher from
Add the following to your top-level build.gradle file:
allprojects {
repositories {
google()
mavenCentral()
maven { url 'https://androidx.dev/snapshots/builds/11193231/artifacts/repository' }
}
}
Together with the following in your macrobench module build.gradle:
dependencies {
implementation "androidx.benchmark:benchmark-macro-junit4:1.3.0-SNAPSHOT"
}
If this addresses the problem for you, we can release a bugfix release that includes this change.
The common case where this likely occurs is from
Note though that the original report in Choreographer#doFrame <frameid>
. Since I didn't have a trace or device to reproduce that string on, I just took the first string after "doframe" in that case as that works for
dv...@gmail.com <dv...@gmail.com> #6
maybe this fix should introduce a depth argument to control which depth level of doFrame to use.
cc...@google.com <cc...@google.com> #7
It should be more common for apps/OS to add trace sections (even above doFrame
) than it is for the OS to modify them, so I'd prefer to limit filtering based on content of the slice rather than depth.
While that would have avoided the #doFrame - resynced to
issue, the change above matches how upstream Perfetto rejects those slices.
pr...@google.com <pr...@google.com> #8
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.benchmark:benchmark-macro:1.3.0-alpha01
Description
Component used: Macrobenchmark/FrameTimingMetric Version used: latest version Devices/Android versions reproduced on: android 13
I used Macrobenchmark to write a cold launching testcase .
I was collecting FrameTimingMetric by passing FrameTimingMetric in measureRepeated method.(please look screenshot I attach below). However I get the exception thrown by require statement.
I debugged the testcase, found that FrameId of Choreographer#doFrame is null.(please look screenshot I attach below)
because of the last substring divided by empty string of choreographer#doFrame is frame time ,not frameId.
could you fix that?
If this is a bug in the library, we would appreciate if you could attach: