Bug#797227: segfault - gst_memory_unmap, libgstreamer

[Vincent Lefevre]

On 2015-08-29 08:41:21 +0900, Mike Hommey wrote:
> On Sat, Aug 29, 2015 at 12:27:02AM +0200, Vincent Lefevre wrote:
> > On 2015-08-29 00:17:06 +0200, Vincent Lefevre wrote:
> > > On 2015-08-28 19:34:53 +0100, jnqnfe wrote:
> > > > Package: iceweasel
> > > > Version: 38.2.1esr-1
> > > > Severity: grave
> > > > 
> > > > The latest iceweasel update causes it to segfault shortly after loading
> > > > it.
> > > 
> > > I don't have any problem on my side (also an x86_64 machine).
> > 
> > I can reproduce the segmentation fault after installing
> > gstreamer1.0-plugins-bad and opening:
> > 
> >   https://vimeo.com/55640554
> > 
> > I would say that's a plugin bug, not an iceweasel bug.
> 
> Can't reproduce here under those conditions, what version of gstreamer
> are you using?

gstreamer1.0-plugins-bad 1.4.5-2+b2

I forgot, to make Iceweasel crash, I also need to play the video.
As soon as I click on the play button, it crashes.

With valgrind, it crashes before the video is played. After thousands
of errors (due to GTK?):

==24014== Invalid free() / delete / delete[] / realloc()
==24014==    at 0x4C2A360: operator delete(void*) (vg_replace_malloc.c:507)
==24014==    by 0x8687D44: ??? (in /usr/lib/iceweasel/libxul.so)
==24014==    by 0xFFEFF4277: ???
==24014==    by 0x47D8A39F: ???
==24014==    by 0xF00000044: ???
==24014==    by 0xDFFFFFFFF: ???
==24014==    by 0x1DC0000002E: ???
==24014==    by 0x157: ???
==24014==    by 0x46C264DF: ???
==24014==    by 0x1DB: ???
==24014==    by 0x47D8A35F: ???
==24014==    by 0x700000006: ???
==24014==  Address 0x47d8a3c0 is not stack'd, malloc'd or (recently) free'd
==24014== 
==24014== 
==24014== HEAP SUMMARY:
==24014==     in use at exit: 167,383 bytes in 1,809 blocks
==24014==   total heap usage: 2,206 allocs, 398 frees, 199,671 bytes allocated
==24014== 
==24014== LEAK SUMMARY:
==24014==    definitely lost: 0 bytes in 0 blocks
==24014==    indirectly lost: 0 bytes in 0 blocks
==24014==      possibly lost: 0 bytes in 0 blocks
==24014==    still reachable: 167,383 bytes in 1,809 blocks
==24014==         suppressed: 0 bytes in 0 blocks
==24014== Rerun with --leak-check=full to see details of leaked memory
==24014== 
==24014== For counts of detected and suppressed errors, rerun with: -v
==24014== ERROR SUMMARY: 213015 errors from 16069 contexts (suppressed: 3 from 1)

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)