From: Nikolay Dimitrov <picmaster@mail.bg>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Prabhu Sundararaj <B36876@freescale.com>
Subject: Re: Chromium layout rendering issue
Date: Sun, 10 May 2015 14:45:26 +0300 [thread overview]
Message-ID: <554F44D6.3050702@mail.bg> (raw)
In-Reply-To: <554CBAE9.6070306@mail.bg>
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
next prev parent reply other threads:[~2015-05-10 11:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 2:41 Chromium layout rendering issue Nikolay Dimitrov
2015-05-08 12:49 ` Otavio Salvador
2015-05-08 13:19 ` Tiago.Velasque
2015-05-08 13:33 ` Otavio Salvador
2015-05-12 14:10 ` Tiago.Velasque
2015-05-08 13:32 ` Nikolay Dimitrov
2015-05-10 11:45 ` Nikolay Dimitrov [this message]
2015-05-11 18:06 ` Prabhu S
2015-05-11 19:38 ` Gary Thomas
2015-05-12 19:41 ` Nikolay Dimitrov
2015-05-08 22:47 ` Gary Thomas
2015-05-08 22:52 ` Eric Nelson
2015-05-08 23:29 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=554F44D6.3050702@mail.bg \
--to=picmaster@mail.bg \
--cc=B36876@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.