Bug#788708: Bug#797385: iceweasel crash loading a youtube page.

Agustin Martin agmartin at debian.org
Thu Nov 12 17:08:04 UTC 2015


On Tue, Sep 01, 2015 at 10:08:49AM +0000, Adrin wrote:
> On Tue, 1 Sep 2015 at 01:30 Mike Hommey <mh at glandium.org> wrote:
> 
> > On Sun, Aug 30, 2015 at 11:12:52AM +0000, Adrin wrote:
> > > Program received signal SIG38, Real-time event 38.
> > > 0x00007ffff4546e23 in js::Shape::search (cx=cx at entry=0x7ffff6b5c990,
> > start=0x7fffd07576f0, id=..., pentry=pentry at entry=0x7fffffff6f00,
> > adding=adding at entry=false) at
> > /tmp/buildd/iceweasel-38.2.1esr/js/src/vm/Shape-inl.h:82
> > > 82    /tmp/buildd/iceweasel-38.2.1esr/js/src/vm/Shape-inl.h: No such
> > file or directory.
> >
> > SIG38 is not a crash. Try to "continue" until you get an actual crash.
> >
> > Mike
> >
> 
> Ok. Here's another try. This time I get the seg fault.
> 
> Program received signal SIGSEGV, Segmentation fault.
> 
> Adrin.

> $ MOZILLA_DISABLE_PLUGINS=1 gdb --args iceweasel
[...]
> #16 0x00007ffff7bc70a4 in start_thread (arg=0x7fffa2afe700) at pthread_create.c:309
>         __res = <optimized out>
>         pd = 0x7fffa2afe700
>         now = <optimized out>
>         unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140735922824960, -8431668617060337543, 0, 140737354125408, 140737193347328, 140735922824960, 8431854847888668793, 8431685629440768121}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
>         not_first_call = <optimized out>
>         pagesize_m1 = <optimized out>
>         sp = <optimized out>
>         freesize = <optimized out>
>         __PRETTY_FUNCTION__ = "start_thread"
> #17 0x00007ffff707c07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
> 

Hi, Adrin and Sebastian, yet another candidate for bug merging and closing,

#797385: iceweasel crash loading a youtube page.

As already pointed out by Mike Hommey this seems very close to #797227.

Last part of your backtrace seems similar to the backtrace reported
in https://bugs.debian.org/797227, caused by the same problem
as https://bugs.debian.org/788708 (cc'ed) in gstreamer1.0-plugins-bad
package and already fixed in testing/sid with gstreamer1.0-plugins-bad
1.4.5-3 or higher.

Which Debian suite (jesie/testing/sid) is running the system showing the
problem? Does it mix suites?

Is the problem still reproducible? Which gstreamer1.0-plugins-bad version is
installed?

Thanks in advance,

Regards,

-- 
Agustin



More information about the pkg-gstreamer-maintainers mailing list