Rendering problem of accelerated canvas with android emulator in CI
Categories
(Core :: Graphics, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: sotaro, Assigned: sotaro)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
Found during Bug 1794380.
With android emulator in CI, accelerated canvas rendering had problems. The problems did not happen with android hardware in CI.
https://treeherder.mozilla.org/jobs?repo=try&revision=0e9b0fd6f7fdf62e6b2a259f98cfb6326df5bc3f
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
•
|
||
Updating emulator version became simple by Bug 1718341. Then just updating emulator version caused a lot of test failure.
Assignee | ||
Comment 2•1 year ago
|
||
Latest Android emulator 33 addressed some test failures of accelerated canvas. But test failures of R-swr-nofis was not addressed.
Assignee | ||
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Sotaro, do you know whether accelerated canvas works on a device running Android 7 (SDK level 24)? ie is it actually an emulator problem, or is it a problem with older versions of Android?
Assignee | ||
Comment 4•1 year ago
•
|
||
I do not have an Android 7 device, but it should be an emulator specific problem.
From Bug 1794380 comment9, Android 8.0 Pixel2 did not cause the problem. By modifying test, it seems to possible to check if accelerated canvas works on Android 7.0 MotoG5.
Assignee | ||
Comment 5•1 year ago
•
|
||
From android 25 emulator, the followings R-nofis tests' failures were addressed. But several failures of R-swr-nofis were not addressed.
layout/reftests/border-radius/clipping-4-canvas.html
layout/reftests/border-radius/clipping-5-refc.html
layout/reftests/border-radius/intersecting-clipping-1-canvas.html
layout/reftests/border-radius/intersecting-clipping-1-refc.html
Assignee | ||
Comment 6•1 year ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #5)
But several failures of R-swr-nofis were not addressed.
It was caused by current implementation of RenderAndroidSurfaceTextureHost. On android emulator, single buffer mode SurfaceTexture is not used. Since single buffer mode SurfaceTexture does not work on Android Emulator.
When SurfaceTexture is not single buffer mode, RenderAndroidSurfaceTextureHost calls mSurfTex->UpdateTexImage() in RenderAndroidSurfaceTextureHost::Lock(). It is necessary for video playback with hardware WebRender. But it does not work with WebRender (Software OpenGL).
Assignee | ||
Comment 7•1 year ago
|
||
Assignee | ||
Comment 8•1 year ago
|
||
Updated•1 year ago
|
Assignee | ||
Comment 9•1 year ago
|
||
Assignee | ||
Comment 10•1 year ago
•
|
||
accelerated canvas seemed to cause timeout failures in Wd1 mda1 mda2 of debug build on Android emulator.
Android emulator does not use hardware GPU. It seems to be related.
Updated•1 year ago
|
Assignee | ||
Comment 11•1 year ago
|
||
Updated•1 year ago
|
Comment 12•1 year ago
|
||
Pushed by sikeda.birchill@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d42a610802e0 Enable accelerated canvas on Android nightly r=lsalzman,gfx-reviewers,jmaher
Comment 13•1 year ago
|
||
bugherder |
Description
•