Fixed
Status Update
No update yet.
Comments
cc...@google.com
Thanks for reporting. We will look into the issue and update the status here.
cc...@google.com
Hi Thanks for reporting the issue. To have more context, can you help provide the following information ?
-
Can you show us how you configure the ImageCapture in the codes ?
-
Did you enable CameraX Extensions ?
-
so the occurrence rate is like 20%, right ?
ap...@google.com
Thanks for your response.
Sure. I can provide more data.
1.
ImageCapture.Builder builder = new ImageCapture.Builder();
builder.setCaptureMode(ImageCapture.CAPTURE_MODE_MINIMIZE_LATENCY);
if (!extensionAvailable) {
builder.setBufferFormat(ImageFormat.YUV_420_888);
}
imageCapture = builder.build();
UseCaseGroup useCaseGroup = new UseCaseGroup.Builder()
.addUseCase(preview)
.addUseCase(imageCapture)
.setViewPort(viewPort)
.build();
cameraProvider.unbindAll();
camera = cameraProvider.bindToLifecycle(this, cameraSelector, useCaseGroup);
-
Yes, Extensions are enabled, which means that the code is not configuring the buffer format and therefore will use the JPEG format. If I disable the extensions, than the error disapears. But I think its more a jpeg format issue then an extension problem.
-
Yes, occurrence rate is 20%.
Description
Version used: 1.1.0-beta01
Devices/Android versions reproduced on: any
When clicking on link to Stack Sampling Trace or Method Sampling Trace, it sometimes doesn't open proper trace file.
It happens when the profiling session was already opened in AS profiler.
This could be resolved with attaching datetime to the profiling file.
This would also improve the file not being overwritten with every benchmark run (+ we do the same thing with perfetto-trace).
Question is whether to do the same for benchmarkData.json?