empathy __memcmp_sse4_1: empathy-call was killed by signal 11 (SIGSEGV)

Bug #1241486 reported by Oleksij Rempel
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
x264
Unknown
Unknown
x264 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

If i start video call, empathy-call will die on this function __memcmp_sse4_1
Initial problem is in libx264-123 and can be reproduced with "gst-launch-1.0 -v v4l2src ! x264enc ! fakesink" too.

This bug exist only on some CPUs. For example same version works on i5-3317U but fail i7-2677M.

Since libx264-123 really old, i assume never version may fix this crash.

For empathy, best workaround is to remove gstreamer1.0-plugins-ugly together with libx264-123.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: libx264-123 2:0.123.2189+git35cf912-1
Uname: Linux 3.12.0-rc3-wl x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Fri Oct 18 12:18:01 2013
Dependencies:
 gcc-4.8-base 4.8.1-10ubuntu8
 libc6 2.17-93ubuntu4
 libgcc1 1:4.8.1-10ubuntu8
 multiarch-support 2.17-93ubuntu4
InstallationDate: Installed on 2013-10-09 (9 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
MarkForUpload: True
SourcePackage: x264
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Oleksij Rempel (olerem) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in x264 (Ubuntu):
status: New → Confirmed
Revision history for this message
borgotretre (borgotretre) wrote :
Revision history for this message
Sander Brandenburg (sander-brandenburg) wrote :

I experienced the same problem with libx264 (2:0.123.2189+git35) using ffmpeg.

After reading http://ffmpeg.org/pipermail/ffmpeg-devel/2013-March/141083.html I added '-fno-aggressive-loop-optimizations' to CFLAGS and libx264 does not crash on initialization anymore.

Revision history for this message
Oleksij Rempel (olerem) wrote :

Thank you Sander,
it fixes this issue for me.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.