Chromium layout rendering issue

Chromium layout rendering issue

[Nikolay Dimitrov]

Hi guys,

I'm testing Chromium v40 on dizzy for some weeks, and there's an issue
with the layout rendering - the renderer doesn't respect the widgets
sizes and draws them one over the other, instead of one next to the
other. This is most easily observed on google's search page where the
words in the upper text row gets squashed on the right, making one big mess.

This was observed on a customer board with tons of patches everywhere. I
tried to remove DV's gstreamer-imx patches from the chromium build to
see whether they trigger the behavior, but nope. I built a half-patched
dizzy for sabresd running pristine FSL kernel, still nope. Then I tried
unmodified fido on sabresd and the problem is gone.

So I have 2 questions:
1. The probability that someone knows what's the actual issue is close
to minus infinity, but at least did someone observed similar behavior?
If needed, I can snap photos to visually demonstrate the issue.

2. Chromium on sabresd & fido gave me at least 1 interesting warning
about GPU being frozen and pending reset in 10s. I haven't seen such
error, but this makes me highly concerned about porting my stuff to
fido. Did someone see such error messages?

Thanks in advance. Regards,
Nikolay

Re: Chromium layout rendering issue

[Otavio Salvador]

On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
...
> So I have 2 questions:
> 1. The probability that someone knows what's the actual issue is close
> to minus infinity, but at least did someone observed similar behavior?
> If needed, I can snap photos to visually demonstrate the issue.

I have customers using it in Dizzy and I didn't see the error. Please
check today's meta-browser as I merged a fix from Khem which address
some installation issues.

> 2. Chromium on sabresd & fido gave me at least 1 interesting warning
> about GPU being frozen and pending reset in 10s. I haven't seen such
> error, but this makes me highly concerned about porting my stuff to
> fido. Did someone see such error messages?

Prabhu?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Chromium layout rendering issue

[Tiago.Velasque]

[-- Attachment #1.1: Type: text/plain, Size: 1879 bytes --]

I actually did notice it but since I was just playing around with the 
images didn't expend much time trying to solve it.

Regards,
Tiago Velasque
Field Application and Sales Engineer
Mobile: +55 11 99327-9023
Email: tiago.velasque@congatec.com


congatec  |   6262 Ferris Square  |  San Diego CA  92121  |  USA  |  
www.congatec.us





From:   Otavio Salvador <otavio@ossystems.com.br>
To:     Nikolay Dimitrov <picmaster@mail.bg>, Prabhu Sundararaj 
<B36876@freescale.com>, 
Cc:     "meta-freescale@yoctoproject.org" 
<meta-freescale@yoctoproject.org>
Date:   05/08/2015 09:51 AM
Subject:        Re: [meta-freescale] Chromium layout rendering issue
Sent by:        meta-freescale-bounces@yoctoproject.org



On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov <picmaster@mail.bg> 
wrote:
...
> So I have 2 questions:
> 1. The probability that someone knows what's the actual issue is close
> to minus infinity, but at least did someone observed similar behavior?
> If needed, I can snap photos to visually demonstrate the issue.

I have customers using it in Dizzy and I didn't see the error. Please
check today's meta-browser as I merged a fix from Khem which address
some installation issues.

> 2. Chromium on sabresd & fido gave me at least 1 interesting warning
> about GPU being frozen and pending reset in 10s. I haven't seen such
> error, but this makes me highly concerned about porting my stuff to
> fido. Did someone see such error messages?

Prabhu?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
-- 
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


[-- Attachment #1.2: Type: text/html, Size: 3763 bytes --]

[-- Attachment #2: Type: image/jpeg, Size: 21632 bytes --]

Re: Chromium layout rendering issue

[Otavio Salvador]

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

On Fri, May 8, 2015 at 10:19 AM, <Tiago.Velasque@congatec.com> wrote:

> I actually did notice it but since I was just playing around with the
> images didn't expend much time trying to solve it.
>

For Dizzy, use GCC 4.8 when building. Fido 4.9 is fine IIRC.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

[-- Attachment #2: Type: text/html, Size: 1120 bytes --]

Re: Chromium layout rendering issue

[Tiago.Velasque]

[-- Attachment #1.1: Type: text/plain, Size: 1185 bytes --]

I'm on Dizzy and GCC 4.8 already.

Regards,
Tiago Velasque
Field Application and Sales Engineer
Mobile: +55 11 99327-9023
Email: tiago.velasque@congatec.com


congatec  |   6262 Ferris Square  |  San Diego CA  92121  |  USA  |  
www.congatec.us





From:   Otavio Salvador <otavio@ossystems.com.br>
To:     Tiago Velasque <Tiago.Velasque@congatec.com>, 
Cc:     Prabhu Sundararaj <B36876@freescale.com>, 
"meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>, 
meta-freescale-bounces@yoctoproject.org, Nikolay Dimitrov 
<picmaster@mail.bg>
Date:   05/08/2015 10:34 AM
Subject:        Re: [meta-freescale] Chromium layout rendering issue
Sent by:        otavio.salvador@gmail.com





On Fri, May 8, 2015 at 10:19 AM, <Tiago.Velasque@congatec.com> wrote:
I actually did notice it but since I was just playing around with the 
images didn't expend much time trying to solve it. 

For Dizzy, use GCC 4.8 when building. Fido 4.9 is fine IIRC.
 
-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

[-- Attachment #1.2: Type: text/html, Size: 3178 bytes --]

[-- Attachment #2: Type: image/jpeg, Size: 21632 bytes --]

Re: Chromium layout rendering issue

[Nikolay Dimitrov]

Hi Otavio,

On 05/08/2015 03:49 PM, Otavio Salvador wrote:
> On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov
> <picmaster@mail.bg> wrote: ...
>> So I have 2 questions: 1. The probability that someone knows what's
>> the actual issue is close to minus infinity, but at least did
>> someone observed similar behavior? If needed, I can snap photos to
>> visually demonstrate the issue.
>
> I have customers using it in Dizzy and I didn't see the error.
> Please check today's meta-browser as I merged a fix from Khem which
> address some installation issues.

FYI - as explained, this visual glitch is 100% reproducible from
official Yocto code on SabreSD, by just opening the Google's front
search page.

My customer changed their in-house app to avoid the visual glitch, but
there is additional 3rd-party web-content that needs to be displayed,
and we can't do anything about it.

I'll check later today the layer updates and will ping back.

>> 2. Chromium on sabresd & fido gave me at least 1 interesting
>> warning about GPU being frozen and pending reset in 10s. I haven't
>>  seen such error, but this makes me highly concerned about porting
>>  my stuff to fido. Did someone see such error messages?
>
> Prabhu?
>

Regards,
Nikolay

Re: Chromium layout rendering issue

[Nikolay Dimitrov]

Hi Otavio,

On 05/08/2015 04:32 PM, Nikolay Dimitrov wrote:
> Hi Otavio,
>
> On 05/08/2015 03:49 PM, Otavio Salvador wrote:
>> On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov
>> <picmaster@mail.bg> wrote: ...
>>> So I have 2 questions: 1. The probability that someone knows
>>> what's the actual issue is close to minus infinity, but at least
>>> did someone observed similar behavior? If needed, I can snap
>>> photos to visually demonstrate the issue.
>>
>> I have customers using it in Dizzy and I didn't see the error.
>> Please check today's meta-browser as I merged a fix from Khem
>> which address some installation issues.
>
> FYI - as explained, this visual glitch is 100% reproducible from
> official Yocto code on SabreSD, by just opening the Google's front
> search page.
>
> My customer changed their in-house app to avoid the visual glitch,
> but there is additional 3rd-party web-content that needs to be
> displayed, and we can't do anything about it.
>
> I'll check later today the layer updates and will ping back.

The issue is not affected by these updates. Here are some
photos/screenshots to see the visual glitch in action:


Device screen, broken layout in upper-right corner (http://google.com)
http://postimg.org/image/biangrz0v

PC screenshot, proper layout (http://google.com)
http://postimg.org/image/oxxo687in

Device screen, broken layout in upper part of the screen
(http://html5test.com)
http://postimg.org/image/czw3sc3rj

PC screenshot, proper layout (http://html5test.com)
http://postimg.org/image/cym5yx1xr


>>> 2. Chromium on sabresd & fido gave me at least 1 interesting
>>> warning about GPU being frozen and pending reset in 10s. I
>>> haven't seen such error, but this makes me highly concerned about
>>> porting my stuff to fido. Did someone see such error messages?
>>
>> Prabhu?

Regards,
Nikolay

Re: Chromium layout rendering issue

[Prabhu S]

[-- Attachment #1: Type: text/plain, Size: 2602 bytes --]

Verified with dizzy + imx-gpu-viv 5.0.11P4 driver and do not see any
issues. So I believe it is not GPU driver regression.

I'm not able to start chromium to reproduce the issue with the
http://boundarydevices.com/i-mx6-kernel-3-10-53/ image

Can someone try with --disable-gpu ?

 or image to reproduce on sabresd?


On Sun, May 10, 2015 at 6:45 AM, Nikolay Dimitrov <picmaster@mail.bg> wrote:

> Hi Otavio,
>
> On 05/08/2015 04:32 PM, Nikolay Dimitrov wrote:
>
>> Hi Otavio,
>>
>> On 05/08/2015 03:49 PM, Otavio Salvador wrote:
>>
>>> On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov
>>> <picmaster@mail.bg> wrote: ...
>>>
>>>> So I have 2 questions: 1. The probability that someone knows
>>>> what's the actual issue is close to minus infinity, but at least
>>>> did someone observed similar behavior? If needed, I can snap
>>>> photos to visually demonstrate the issue.
>>>>
>>>
>>> I have customers using it in Dizzy and I didn't see the error.
>>> Please check today's meta-browser as I merged a fix from Khem
>>> which address some installation issues.
>>>
>>
>> FYI - as explained, this visual glitch is 100% reproducible from
>> official Yocto code on SabreSD, by just opening the Google's front
>> search page.
>>
>> My customer changed their in-house app to avoid the visual glitch,
>> but there is additional 3rd-party web-content that needs to be
>> displayed, and we can't do anything about it.
>>
>> I'll check later today the layer updates and will ping back.
>>
>
> The issue is not affected by these updates. Here are some
> photos/screenshots to see the visual glitch in action:
>
>
> Device screen, broken layout in upper-right corner (http://google.com)
> http://postimg.org/image/biangrz0v
>
> PC screenshot, proper layout (http://google.com)
> http://postimg.org/image/oxxo687in
>
> Device screen, broken layout in upper part of the screen
> (http://html5test.com)
> http://postimg.org/image/czw3sc3rj
>
> PC screenshot, proper layout (http://html5test.com)
> http://postimg.org/image/cym5yx1xr
>
>
>
>  2. Chromium on sabresd & fido gave me at least 1 interesting
>>>> warning about GPU being frozen and pending reset in 10s. I
>>>> haven't seen such error, but this makes me highly concerned about
>>>> porting my stuff to fido. Did someone see such error messages?
>>>>
>>>
>>> Prabhu?
>>>
>>
> Regards,
> Nikolay
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

[-- Attachment #2: Type: text/html, Size: 4628 bytes --]

Re: Chromium layout rendering issue

[Gary Thomas]

On 2015-05-11 12:06, Prabhu S wrote:
> Verified with dizzy + imx-gpu-viv 5.0.11P4 driver and do not see any issues. So I believe it is not GPU driver regression.
>
> I'm not able to start chromium to reproduce the issue with the http://boundarydevices.com/i-mx6-kernel-3-10-53/ image

Why can't you start chromium with this image?

>
> Can someone try with --disable-gpu ?

I tried it on the SabreLite and chrome no longer crashes and it seems to render correctly.

Sure looks like a GPU issue to me [if disabling it "fixes" the problem]

>
>   or image to reproduce on sabresd?
>
>
> On Sun, May 10, 2015 at 6:45 AM, Nikolay Dimitrov <picmaster@mail.bg <mailto:picmaster@mail.bg>> wrote:
>
>     Hi Otavio,
>
>     On 05/08/2015 04:32 PM, Nikolay Dimitrov wrote:
>
>         Hi Otavio,
>
>         On 05/08/2015 03:49 PM, Otavio Salvador wrote:
>
>             On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov
>             <picmaster@mail.bg <mailto:picmaster@mail.bg>> wrote: ...
>
>                 So I have 2 questions: 1. The probability that someone knows
>                 what's the actual issue is close to minus infinity, but at least
>                 did someone observed similar behavior? If needed, I can snap
>                 photos to visually demonstrate the issue.
>
>
>             I have customers using it in Dizzy and I didn't see the error.
>             Please check today's meta-browser as I merged a fix from Khem
>             which address some installation issues.
>
>
>         FYI - as explained, this visual glitch is 100% reproducible from
>         official Yocto code on SabreSD, by just opening the Google's front
>         search page.
>
>         My customer changed their in-house app to avoid the visual glitch,
>         but there is additional 3rd-party web-content that needs to be
>         displayed, and we can't do anything about it.
>
>         I'll check later today the layer updates and will ping back.
>
>
>     The issue is not affected by these updates. Here are some
>     photos/screenshots to see the visual glitch in action:
>
>
>     Device screen, broken layout in upper-right corner (http://google.com)
>     http://postimg.org/image/biangrz0v
>
>     PC screenshot, proper layout (http://google.com)
>     http://postimg.org/image/oxxo687in
>
>     Device screen, broken layout in upper part of the screen
>     (http://html5test.com)
>     http://postimg.org/image/czw3sc3rj
>
>     PC screenshot, proper layout (http://html5test.com)
>     http://postimg.org/image/cym5yx1xr
>
>
>
>                 2. Chromium on sabresd & fido gave me at least 1 interesting
>                 warning about GPU being frozen and pending reset in 10s. I
>                 haven't seen such error, but this makes me highly concerned about
>                 porting my stuff to fido. Did someone see such error messages?
>
>
>             Prabhu?
>
>
>     Regards,
>     Nikolay
>     --
>     _______________________________________________
>     meta-freescale mailing list
>     meta-freescale@yoctoproject.org <mailto:meta-freescale@yoctoproject.org>
>     https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Chromium layout rendering issue

[Nikolay Dimitrov]

Hi guys,

FYI, the layout issue is not observed when using Yocto Fido and FSL
kernel 3.10.53. I wasted almost 2 days of updating Chromium
dependencies, but lost interest and decided to entirely move to Fido.

I've discovered another issue introduced by the latest meta-browser
updates - Chromium fails to start due to missing files. This is now
fixed, and a patch was submitted to openembedded-devel ML. I can't
provide a link there, as my green-horn posts needs to be approved, but
here's a Github link to the patch:

https://github.com/picmaster/meta-browser/commit/d80d6f62b07aeaefaab965b2c885e78806ca4878

During the testing of my latest build, Chromium again froze for about
10s, so I'll keep an eye on it to see what triggers it, and share
if/when I have more info.

Kind regards,
Nikolay

Re: Chromium layout rendering issue

[Gary Thomas]

On 2015-05-08 06:49, Otavio Salvador wrote:
> On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
> ...
>> So I have 2 questions:
>> 1. The probability that someone knows what's the actual issue is close
>> to minus infinity, but at least did someone observed similar behavior?
>> If needed, I can snap photos to visually demonstrate the issue.
>
> I have customers using it in Dizzy and I didn't see the error. Please
> check today's meta-browser as I merged a fix from Khem which address
> some installation issues.
>
>> 2. Chromium on sabresd & fido gave me at least 1 interesting warning
>> about GPU being frozen and pending reset in 10s. I haven't seen such
>> error, but this makes me highly concerned about porting my stuff to
>> fido. Did someone see such error messages?
>
> Prabhu?
>

I just rebuilt Chrome with the latest meta-browser (and meta-fsl-arm-*)
There are many rendering problems on the Google main page and then I
get these errors:

[872:872:0508/165904:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
[896:896:0508/165907:ERROR:sandbox_linux.cc(301)] InitializeSandbox() called with multiple threads in process gpu-process
Fontconfig warning: FcPattern object size does not accept value 9(i)
[958:958:0508/165913:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
[870:890:0508/165930:ERROR:channel.cc(258)] RawChannel read error (connection broken)
[896:906:0508/165943:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 10000 ms.
[870:870:0508/165943:ERROR:gpu_channel_host.cc(185)] Failed to send GpuChannelMsg_CreateOffscreenCommandBuffer.
[870:870:0508/165943:ERROR:webgraphicscontext3d_command_buffer_impl.cc(230)] Failed to initialize command buffer.
[1005:1006:0508/165955:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 10000 ms.
getrlimit(RLIMIT_NOFILE) failed
getrlimit(RLIMIT_NOFILE) failed

This is on a board using the Boundary Devices 3.10.53 kernel
(I don't have a board here that runs a "pure" FSLC kernel)
but as far as I can tell the BD kernel is the FSLC kernel
with some of their own patches, mostly to do with cameras.

Anything I can look for/test?

Also note that this kernel has lots of [rendering] problems
with other applications.  For example, if I run the new Gstreamer-1.0
based "media player" to play a video, it will bring up the window but
not render any video frames or sometimes render a few and then freeze.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Chromium layout rendering issue

[Eric Nelson]

Hi Gary,

On 05/08/2015 03:47 PM, Gary Thomas wrote:
> On 2015-05-08 06:49, Otavio Salvador wrote:
>> On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov <picmaster@mail.bg>
>> wrote:
>> ...
>>> So I have 2 questions:
>>> 1. The probability that someone knows what's the actual issue is close
>>> to minus infinity, but at least did someone observed similar behavior?
>>> If needed, I can snap photos to visually demonstrate the issue.
>>
>> I have customers using it in Dizzy and I didn't see the error. Please
>> check today's meta-browser as I merged a fix from Khem which address
>> some installation issues.
>>
>>> 2. Chromium on sabresd & fido gave me at least 1 interesting warning
>>> about GPU being frozen and pending reset in 10s. I haven't seen such
>>> error, but this makes me highly concerned about porting my stuff to
>>> fido. Did someone see such error messages?
>>
>> Prabhu?
>>
> 
> I just rebuilt Chrome with the latest meta-browser (and meta-fsl-arm-*)
> There are many rendering problems on the Google main page and then I
> get these errors:
> 
> [872:872:0508/165904:ERROR:image_metadata_extractor.cc(111)] Couldn't
> load libexif.
> [896:896:0508/165907:ERROR:sandbox_linux.cc(301)] InitializeSandbox()
> called with multiple threads in process gpu-process
> Fontconfig warning: FcPattern object size does not accept value 9(i)
> [958:958:0508/165913:ERROR:image_metadata_extractor.cc(111)] Couldn't
> load libexif.
> [870:890:0508/165930:ERROR:channel.cc(258)] RawChannel read error
> (connection broken)
> [896:906:0508/165943:ERROR:gpu_watchdog_thread.cc(253)] The GPU process
> hung. Terminating after 10000 ms.
> [870:870:0508/165943:ERROR:gpu_channel_host.cc(185)] Failed to send
> GpuChannelMsg_CreateOffscreenCommandBuffer.
> [870:870:0508/165943:ERROR:webgraphicscontext3d_command_buffer_impl.cc(230)]
> Failed to initialize command buffer.
> [1005:1006:0508/165955:ERROR:gpu_watchdog_thread.cc(253)] The GPU
> process hung. Terminating after 10000 ms.
> getrlimit(RLIMIT_NOFILE) failed
> getrlimit(RLIMIT_NOFILE) failed
> 
> This is on a board using the Boundary Devices 3.10.53 kernel
> (I don't have a board here that runs a "pure" FSLC kernel)
> but as far as I can tell the BD kernel is the FSLC kernel
> with some of their own patches, mostly to do with cameras.
> 

Was this on master or fido?

> Anything I can look for/test?
> 
> Also note that this kernel has lots of [rendering] problems
> with other applications.  For example, if I run the new Gstreamer-1.0
> based "media player" to play a video, it will bring up the window but
> not render any video frames or sometimes render a few and then freeze.
> 
Can you try with the pre-built image here?
	http://boundarydevices.com/i-mx6-kernel-3-10-53/

We didn't see any issues, but mostly ran things from the command-line
and the pre-built Vivante demos to test graphics.

Please advise,


Eric

Re: Chromium layout rendering issue

[Gary Thomas]

On 2015-05-08 16:52, Eric Nelson wrote:
> Hi Gary,
>
> On 05/08/2015 03:47 PM, Gary Thomas wrote:
>> On 2015-05-08 06:49, Otavio Salvador wrote:
>>> On Thu, Apr 30, 2015 at 11:41 PM, Nikolay Dimitrov <picmaster@mail.bg>
>>> wrote:
>>> ...
>>>> So I have 2 questions:
>>>> 1. The probability that someone knows what's the actual issue is close
>>>> to minus infinity, but at least did someone observed similar behavior?
>>>> If needed, I can snap photos to visually demonstrate the issue.
>>>
>>> I have customers using it in Dizzy and I didn't see the error. Please
>>> check today's meta-browser as I merged a fix from Khem which address
>>> some installation issues.
>>>
>>>> 2. Chromium on sabresd & fido gave me at least 1 interesting warning
>>>> about GPU being frozen and pending reset in 10s. I haven't seen such
>>>> error, but this makes me highly concerned about porting my stuff to
>>>> fido. Did someone see such error messages?
>>>
>>> Prabhu?
>>>
>>
>> I just rebuilt Chrome with the latest meta-browser (and meta-fsl-arm-*)
>> There are many rendering problems on the Google main page and then I
>> get these errors:
>>
>> [872:872:0508/165904:ERROR:image_metadata_extractor.cc(111)] Couldn't
>> load libexif.
>> [896:896:0508/165907:ERROR:sandbox_linux.cc(301)] InitializeSandbox()
>> called with multiple threads in process gpu-process
>> Fontconfig warning: FcPattern object size does not accept value 9(i)
>> [958:958:0508/165913:ERROR:image_metadata_extractor.cc(111)] Couldn't
>> load libexif.
>> [870:890:0508/165930:ERROR:channel.cc(258)] RawChannel read error
>> (connection broken)
>> [896:906:0508/165943:ERROR:gpu_watchdog_thread.cc(253)] The GPU process
>> hung. Terminating after 10000 ms.
>> [870:870:0508/165943:ERROR:gpu_channel_host.cc(185)] Failed to send
>> GpuChannelMsg_CreateOffscreenCommandBuffer.
>> [870:870:0508/165943:ERROR:webgraphicscontext3d_command_buffer_impl.cc(230)]
>> Failed to initialize command buffer.
>> [1005:1006:0508/165955:ERROR:gpu_watchdog_thread.cc(253)] The GPU
>> process hung. Terminating after 10000 ms.
>> getrlimit(RLIMIT_NOFILE) failed
>> getrlimit(RLIMIT_NOFILE) failed
>>
>> This is on a board using the Boundary Devices 3.10.53 kernel
>> (I don't have a board here that runs a "pure" FSLC kernel)
>> but as far as I can tell the BD kernel is the FSLC kernel
>> with some of their own patches, mostly to do with cameras.
>>
>
> Was this on master or fido?
>
>> Anything I can look for/test?
>>
>> Also note that this kernel has lots of [rendering] problems
>> with other applications.  For example, if I run the new Gstreamer-1.0
>> based "media player" to play a video, it will bring up the window but
>> not render any video frames or sometimes render a few and then freeze.
>>
> Can you try with the pre-built image here?
> 	http://boundarydevices.com/i-mx6-kernel-3-10-53/
>
> We didn't see any issues, but mostly ran things from the command-line
> and the pre-built Vivante demos to test graphics.

Just tried this on my SabreLite.

Chrome - fails just like on my board as reported above
media player (gst-play-1.0) - thinks it's running, but no video

Also, I don't have any audio, neither analog or HDMI

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------