On Wed, Jul 23, 2014 at 12:30:20PM +0200, Fabian Raetz wrote: > On Wed, Jul 23, 2014 at 11:33:44AM +0200, Landry Breuil wrote: > > On Wed, Jul 23, 2014 at 12:01:01AM +0200, Fabian Raetz wrote: > > > On Tue, Jul 22, 2014 at 11:48:18PM +0200, Landry Breuil wrote: > > > > On Tue, Jul 22, 2014 at 11:27:36PM +0200, Fabian Raetz wrote: > > > > > Hi, > > > > > > > > > > i am in the process of testing 5.6 on amd64 and > > > > > noticed that firefox always coredumps while watching > > > > > videos on youtube. > > > > > > > > > > Does someone see this too? > > > > > > > > > > I am uploading the coredumps to google drive. If someone > > > > > want to take a look i will send the links. > > > > > > > > > > I will try on latest snapshot probably next day. > > > > > > > > > > > > > > > @landry: > > > > > I tries to install & test 31-beta from your pkgs > > > > > but they are linked against an older libc. Do you have > > > > > an actual package for me to test? Will firefox 31 make it > > > > > into 5.6? > > > > > > > > No, and yes, probably. > > > > > > > > > Here's a sample backtrace. Have 3 of them, > > > > > all with same backtrace: > > > > > > > > > > Current language: auto; currently asm > > > > > #0 0x00001be7cb2367fa in kill () at <stdin>:2 > > > > > #1 0x00001be70a4e7f44 in XRE_FreeAppData () > > > > > from /usr/local/lib/firefox-30.0/libxul.so.48.0 > > > > > #2 <signal handler called> > > > > > #3 0x00001be7faa71214 in decode_ics () > > > > > from /usr/local/lib/gstreamer-1.0/libgstlibav.so > > > > > > > > Looks like at this point, a signal is raised within gstreamer1 for some > > > > reason, which calls the crash handler in firefox.. > > > > > > Hm, in two cases there was another coredump from "plugin-container" > > > but i didn't know how to get a backtrace from it :( Maybe they have raised > > > the signal? Any hints for me on how to get a backtrace of it? There is > > > no program "plugin-container" on my system. > > > > $pkg_info -L firefox | grep plugin-container > > /usr/local/lib/firefox-31.0/plugin-container > > -.- > > backtrace from plugin_container.core: > > #0 0x000012d8637ea967 in mozalloc_abort () > from /usr/local/lib/firefox-30.0/libmozalloc.so.48.0
> and another one: > > > #0 0x00001d6980704967 in mozalloc_abort () from > /usr/local/lib/firefox-30.0/libmozalloc.so.48.0 bump your limits. Usually, when ffx hits the ulimits (because for some reason a webpage consumes too much memory), it doesnt handle well the case of malloc not returning more memory, and crashes. if you're running with the default ulimit -d of 500Mb, that's probably the cause. Bump it to 1G or 2G. Landry
