Second App launch failure on Renesas M3 board.
Description
Environment
Attachments
Activity
Close for FF 6.0.4 and GG 7.0.0
The issue was the apparently due to the same case mentioned at https://lf-automotivelinux.atlassian.net/browse/SPEC-2080.
After these changes https://github.com/webosose/chromium68/pull/10 to make GLSurfaceWayland (used with in-process-gpu mode) to use wl_surface_frame, we are not being able to reproduce the issue anymore.
Hi @Harunobu Kurokawa san,
We also observed the same behavior during chromium68 porting related to surface information.
I got same issue again and I found thread info using your debug. In another viewpoint, when the issue is happened, it looks like that surface information is not collect.
First app (youtube) has surface 4208, second app uses surface 4243.
surface 4243. the source region is all 0.
m3ulcb:~# LayerManagerControl get surfaces
5 Surface(s):
- Surface 2 (0x2)
- Surface 1 (0x1)
- Surface 3 (0x3)
- Surface 4208 (0x1070)
- Surface 4243 (0x1093)
m3ulcb:~# LayerManagerControl get surface 4243
surface 4243 (0x1093)
---------------------------------------
- created by pid: 3680
- original size: x=0, y=0
- destination region: x=0, y=218, w=1080, h=1488
- source region: x=0, y=0, w=0, h=0
- opacity: 1
- visibility: 1
- frame counter: 0
- on layer: 1001(0x3e9)
m3ulcb:~# LayerManagerControl get surface 4208
surface 4208 (0x1070)
---------------------------------------
- created by pid: 3680
- original size: x=1080, y=1488
- destination region: x=0, y=218, w=1080, h=1488
- source region: x=0, y=0, w=1080, h=1488
- opacity: 1
- visibility: 0
- frame counter: 4
- on layer: 1001(0x3e9)
m3ulcb:~#Hi @Harunobu Kurokawa san,
I noticed that the frequency of second app launch issue is very less after I synced to the latest code base(I did it for chromium68) and then built chromium53.
But still, I was able to reproduce issue 1 out of 5 trials.
Regarding to Q1 > GPU thread running in WebAppMgr process has eglSwapBuffer. @Maksim Sisov working on chromium Wayland stack can give more information about it.
Regarding to Q2 > I have generated WAYLAND_DEBUG logs for both
and
case. As expected, in non working case we have less WALAND_DEBUG logs.
I will share result once WAM with chromium68 is in working condition.
Details
Details
Assignee
Reporter
Fix versions
Contract ID
Components
Priority
Major
Steps to reproduce :
Launch YouTube Application and wait for some time
Click on Home icon.
Launch HVAC-ENACT App.
HVAC-ENACT is not loading.
Hardware: Renesas M3
NOTE: This issue is not reproducible on intel minnowboard boards.