From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <picmaster@mail.bg>
Received: by yocto-www.yoctoproject.org (Postfix, from userid 118)
	id 0E22CE00A1C; Mon, 15 Jun 2015 05:59:33 -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.119 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 mx3.mail.bg (mx3.mail.bg [193.201.172.119])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 87F53E009E5
	for <meta-freescale@yoctoproject.org>;
	Mon, 15 Jun 2015 05:59: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 mx3.mail.bg (Postfix) with ESMTPSA id D9FD9202A7F7;
	Mon, 15 Jun 2015 15:59:26 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default;
	t=1434373167; bh=5jyidFR5FrVD3CsDPm3qC15RJGoDpLWxGmw1M35ub5E=;
	h=Message-ID:Date:From:MIME-Version:To:Subject:References:
	In-Reply-To:Content-Type:Content-Transfer-Encoding;
	b=Azc8pJMKVWSj7UnROER6jlzga8oQXpP2ypfttcuqTZGazQuCz4PKyyHduT5vJUjkj
	78FelChx1MWOt9UWPfxTKt/KvbQlhLrpJTVwhiptK87+NhmRCYk1ogRK1diOiF0yaH
	Mt/yOFJOfAbE1xib31l7MEkLwkxWkGRsyIZ2dupA=
Message-ID: <557ECC2E.7010501@mail.bg>
Date: Mon, 15 Jun 2015 15:59:26 +0300
From: Nikolay Dimitrov <picmaster@mail.bg>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: Greg <grg.moulin@gmail.com>, meta-freescale@yoctoproject.org
References: <5579F20D.5040900@mail.bg>
	<loom.20150615T091917-506@post.gmane.org>
In-Reply-To: <loom.20150615T091917-506@post.gmane.org>
Subject: Re: Chromium crashes on HTML5 video tag
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
	<meta-freescale.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/meta-freescale>,
	<mailto:meta-freescale-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/meta-freescale>
List-Post: <mailto:meta-freescale@yoctoproject.org>
List-Help: <mailto:meta-freescale-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/meta-freescale>,
	<mailto:meta-freescale-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2015 12:59:33 -0000
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Hi Greg,

On 06/15/2015 10:29 AM, Greg wrote:
> Nikolay Dimitrov <picmaster@...> writes:
>
>>
>> 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.
>>
>> Thanks in advance for any ideas. Regards,
>> Nikolay
>
>
> Hi,
>
> I had the same problem and I solved it by moving libffmpegsumo.so from
> /usr/lib/chromium/ to /usr/bin/chromium/.
> I'm now able to play audio and video files using HTML5 tag.

Do you remember which git commit you've used during this observation?

Regards,
Nikolay