From: Nikolay Dimitrov <picmaster@mail.bg>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Chromium layout rendering issue
Date: Fri, 01 May 2015 05:41:31 +0300 [thread overview]
Message-ID: <5542E7DB.2010905@mail.bg> (raw)
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
next reply other threads:[~2015-05-01 2:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 2:41 Nikolay Dimitrov [this message]
2015-05-08 12:49 ` Chromium layout rendering issue 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
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=5542E7DB.2010905@mail.bg \
--to=picmaster@mail.bg \
--cc=meta-freescale@yoctoproject.org \
/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.