From: Michael Hargreaves <mik.hargreaves@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-freescale] Chromium crashes on HTML5 video tag
Date: Thu, 02 Jul 2015 23:10:57 +1000 [thread overview]
Message-ID: <55953861.2050506@gmail.com> (raw)
In-Reply-To: <mailman.5.1435838401.9446.openembedded-devel@lists.openembedded.org>
Hi Nikolay,
On 2/07/2015 10:00 PM, openembedded-devel-request@lists.openembedded.org
wrote:
> Hi Zoltan, On 06/12/2015 09:57 AM, Zoltan Kuscsik wrote:
>> >Do you have a crash log? If not, you should change your build from Release
>> >to Debug and
>> >get some backtraces.
> The chromium debug binary is 3.1GiB, there's no way to run this on my
> ARM target. If you have other suggestions how to extract trace/debug
> info, I would be glad to try them.
>
> Regards,
> Nikolay
I hit a similar issue on intel platform since updating meta-browser. It
wasn't crashing, but was getting the 'Aw, Snap' chromium page on any
html5 video or audio.
It turned out to be because the ffmpeg codecs have been separated into
their own split package.
Adding both 'chromium' and 'chromium-codecs-ffmpeg' to the IMAGE_INSTALL
resolved the issue for me.
Possibly not the same issue, but sounds similar.
Cheers,
Mik.
next parent reply other threads:[~2015-07-02 13:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1435838401.9446.openembedded-devel@lists.openembedded.org>
2015-07-02 13:10 ` Michael Hargreaves [this message]
2015-07-02 20:40 ` [meta-freescale] Chromium crashes on HTML5 video tag Nikolay Dimitrov
2015-06-11 20:39 Nikolay Dimitrov
2015-06-12 6:51 ` [meta-freescale] " Nikolay Dimitrov
2015-06-12 6:57 ` Zoltan Kuscsik
2015-07-02 10:21 ` Nikolay Dimitrov
2015-06-12 10:46 ` Nikolay Dimitrov
2015-06-12 10:51 ` Zoltan Kuscsik
2015-06-12 11:17 ` Nikolay Dimitrov
2015-06-12 11:31 ` Otavio Salvador
2015-06-12 11:42 ` Gary Thomas
2015-06-12 12:08 ` Nikolay Dimitrov
2015-06-12 12:23 ` Gary Thomas
2015-06-12 12:52 ` 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=55953861.2050506@gmail.com \
--to=mik.hargreaves@gmail.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.