From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 3E9DBE009F3; Sun, 10 May 2015 04:45:32 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 87C16E009E2 for ; Sun, 10 May 2015 04:45:28 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id 3758E6000740; Sun, 10 May 2015 14:45:27 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1431258327; bh=8Znsyx/nnVt8LFZm/AMxAZAsrFZNmT93mOc2t3c4+90=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=EI/zfblRv6blQsAw7b5t4cUdE7KM+VaaKOrXo2QAXub5Kys6ZgLOGUZZJ9gW0qZKg PnEFvzFSmdIOuITduVcEkBKZPowhmpQMsyfCCsKVD9A2S9twXE2/b50EnjflJBi4W8 zyGYW5oYp41OGMj6i/ikWsUVqpc7nXdWg0bAF/4g= Message-ID: <554F44D6.3050702@mail.bg> Date: Sun, 10 May 2015 14:45:26 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Otavio Salvador References: <5542E7DB.2010905@mail.bg> <554CBAE9.6070306@mail.bg> In-Reply-To: <554CBAE9.6070306@mail.bg> Cc: "meta-freescale@yoctoproject.org" , Prabhu Sundararaj Subject: Re: Chromium layout rendering issue X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 May 2015 11:45:32 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 >> 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