After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789126 - [x264enc] x264enc plugin report double free corruption
[x264enc] x264enc plugin report double free corruption
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
1.12.2
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-18 02:43 UTC by Lyon
Modified: 2018-01-18 22:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Lyon 2017-10-18 02:43:54 UTC 
When I'm trying to use x264enc to encode a raw file by below command line:
gst-launch-1.0 filesrc location=1920x1080_input.yuv ! videoparse format=2 width=1920 height=1080 framerate=30/1 ! x264enc ! matroskamux ! filesink location=x264enc_1920x1080.mkv

Though the output encoded file can be played, it will report "*** Error in `/usr/bin/gst-launch-1.0': double free or corruption (!prev): 0x0000ffffb0037fc0 ***"  in the end.

Seems the backtrace show corruption is in libx264

Thread 1 "gst-launch-1.0" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at /usr/src/debug/glibc/2.24-r0/git/sysdeps/unix/sysv/linux/raise.c:58
58	}
(gdb) bt

+ Trace 238072

  • #0 __GI_raise
    at /usr/src/debug/glibc/2.24-r0/git/sysdeps/unix/sysv/linux/raise.c line 58
  • #1 __GI_abort
    at /usr/src/debug/glibc/2.24-r0/git/stdlib/abort.c line 89
  • #2 __libc_message
    at /usr/src/debug/glibc/2.24-r0/git/sysdeps/posix/libc_fatal.c line 175
  • #3 malloc_printerr
  • #4 _int_free
    at /usr/src/debug/glibc/2.24-r0/git/malloc/malloc.c line 3902
  • #5 x264_macroblock_thread_free
    from /usr/lib/libx264.so.144 






Comment 1


Sebastian Dröge (slomo)





          2017-10-19 14:03:53 UTC
        



Can you also reproduce it with videotestsrc? Can you provide a valgrind log with --track-origins=yes?






Comment 2


Tim-Philipp Müller





          2018-01-18 22:24:30 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!