shenghao@: Could you take a look at this issue?

I probably won't have cycles to work on this until end of Q4.

Can we untag as a beta blocker and/or find a new owner and/or make it a stable blocker if we don't have resources?

M64 beta is targeted for next Tuesday (12-Dec).  Thanks!

Let's make this a stable blocker.

This is tagged as a P1/Stable blocker.  Let's eval and remove that block if not that priority.  Thx

I tested on celes M63-9931.0.0 and M64-10172.0.0. Chrome camera app spends 5 seconds to start on both of them.

kebalaji@,
What version of M63 did you test that is working fine? What device did you test?

Issue is that some stuck is seen after camera app starts. Observe the actual video in which in 0:15-0:20 camera is getting stuck.

Able to reproduce the issue on 65.0.3311.0/10280.0.0 dev channel Kip, Daisy, Reks and unable to reproduce on 63.0.3239.116/10032.75.0 stable channel Celes.

Thank you!

Deleted: ActualCamera.webm 1.2 MB

	ActualCamera.webm 1.2 MB View Download

Can the bug reproduce on celes on some versions?
Is the bug unreproducible on Kip, Daisy or Reks on some versions?
Comparing the stuck time on different devices is not very helpful to find the root cause.

Issue is reproducible on M65 across all devices(Eg: Kip,Celes,Daisy,Reks etc.,) and not reproducible on M63 stable across all devices(Eg: Kip,Celes,Daisy,Reks etc.,).

Thanks!

I tested on celes M65-10290.0.0, M63-10032.75.0.
Chrome camera app spends 6 seconds from showing a black window to showing the first preview frame.
This bug is not a regression. It's a performance improvement request.
Lowering to P2.

Sheng-hao. Do you mean M63-10032.75.0 also spent 6 seconds to start for you?

Looks like Sheng-hao could not reproduce the issue and kebalaji@ could reproduce the issue.

In any case, it's a bit late for M65. We punted it once to M65 and I'm going to punt it to M66.

Re #15: yes.

Punt to M67 and removed the release blocker label.