From: Nikolay Dimitrov <picmaster@mail.bg>
To: Gary Thomas <gary@mlbassoc.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-freescale] Chromium crashes on HTML5 video tag
Date: Fri, 12 Jun 2015 15:08:42 +0300 [thread overview]
Message-ID: <557ACBCA.40709@mail.bg> (raw)
In-Reply-To: <557AC595.7070402@mlbassoc.com>
Hi Gary,
On 06/12/2015 02:42 PM, Gary Thomas wrote:
> On 2015-06-12 05:31, Otavio Salvador wrote:
>> On Fri, Jun 12, 2015 at 7:46 AM, Nikolay Dimitrov <picmaster@mail.bg>
>> wrote:
>>> On 06/12/2015 09:51 AM, Nikolay Dimitrov wrote:
>>>>
>>>> Adding openembedded guys in the loop.
>>>>
>>>>
>>>> On 06/11/2015 11:39 PM, Nikolay Dimitrov wrote:
>>>>>
>>>>> Hi gang,
>>>>>
>>>>> Chromium tabs are crashing when they see an HTML5 <video> tag, like
>>>>> this one:
>>>>>
>>>>> <video width="320" height="240" controls>
>>>>> <source src="movie.mp4" type="video/mp4">
>>>>> </video>
>>>>>
>>>>> (Code is from http://www.w3schools.com/html/html5_video.asp)
>>>>>
>>>>> I'm pretty sure that this worked fine some weeks ago, so it's a recent
>>>>> regression on Fido, 100% reproducible on imx6q sabresd. At this moment
>>>>> I still can't point to a specific commit in meta-fsl-arm or
>>>>> meta-browser.
>>>
>>>
>>> Commit 30b8d6b3d0d6501c56ef6967a2fa73a3d4bf5fe9 is the last known good
>>> commit. After it the component either doesn't compile, libs are missing
>>> or video tag isn't working.
>>>
>>> Looks like it's a "revert time" for the customer builds...
>>
>> Might be packaging splitting which can have changes. One way to easily
>> track this is using buildhistory and compare both packaged outputs.
>>
>
> It looks to me like that revision updated by 2 major versions of
> Chrome - more likely there are goblins in there than just a packaging
> issue.
Not really. Commit 30b8d6b3d0d6501c56ef6967a2fa73a3d4bf5fe9 is working
OK, as I described. Issues start from the next commit,
355f6d474462996c3bf07d7a72233b6c81cb2e8a.
Regards,
Nikolay
next prev parent reply other threads:[~2015-06-12 12:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 20:39 Chromium crashes on HTML5 video tag Nikolay Dimitrov
2015-06-12 6:51 ` [meta-freescale] " Nikolay Dimitrov
2015-06-12 6:51 ` Nikolay Dimitrov
2015-06-12 6:57 ` [meta-freescale] " Zoltan Kuscsik
2015-06-12 6:57 ` [oe] " Zoltan Kuscsik
2015-07-02 10:21 ` [meta-freescale] " Nikolay Dimitrov
2015-07-02 10:21 ` [oe] " Nikolay Dimitrov
2015-06-12 10:46 ` [meta-freescale] " Nikolay Dimitrov
2015-06-12 10:46 ` Nikolay Dimitrov
2015-06-12 10:51 ` [meta-freescale] " Zoltan Kuscsik
2015-06-12 10:51 ` [oe] " Zoltan Kuscsik
2015-06-12 11:17 ` [meta-freescale] " Nikolay Dimitrov
2015-06-12 11:17 ` [oe] " Nikolay Dimitrov
2015-06-12 11:31 ` [meta-freescale] " Otavio Salvador
2015-06-12 11:31 ` [oe] " Otavio Salvador
2015-06-12 11:42 ` [meta-freescale] " Gary Thomas
2015-06-12 12:08 ` Nikolay Dimitrov [this message]
2015-06-12 12:23 ` Gary Thomas
2015-06-12 12:52 ` Nikolay Dimitrov
2015-06-15 7:29 ` Greg
2015-06-15 12:59 ` Nikolay Dimitrov
2015-06-15 13:33 ` Greg
2015-06-15 14:53 ` Nikolay Dimitrov
[not found] <mailman.5.1435838401.9446.openembedded-devel@lists.openembedded.org>
2015-07-02 13:10 ` [meta-freescale] " Michael Hargreaves
2015-07-02 20:40 ` Nikolay Dimitrov
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=557ACBCA.40709@mail.bg \
--to=picmaster@mail.bg \
--cc=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.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.