HandBrake giving segmentation faults from SBo and Alien's script

moisespedro · 04-12-2014, 08:25 AM

I've installed HandBrake some time ago from SBo but never used it, today while trying to encode a video (with x264 encoder) the softwares crashes and, by running it via terminal, it reported a segmentation fault.

I went on Google and found a few things like this bugreport on Ubuntu.

Because of this part:

Quote:

Configure x264 with "--extra-cflags=-fno-aggressive-loop-optimizations" solves this problem.
Also seems that problem solved in trunk - http://git.videolan.org/?p=x264.git;...eb12504711b94f

I thought that simply using a newer version of the x264 tarball would work, I grabbed Alien's script (that also had the same problem) and edited as this:

Code:

pedro@darkstar:~/Downloads/slackware/alien_repository/handbrake/build$ diff handbrake.SlackBuild /home/pedro/SlackBuilds/14.1/handbrake/handbrake.SlackBuild                                                                                                                                                                
94c94
< X264="r2273-b3065e6"
---
> X264=20140411-2245
156,157c156,157
< SOURCE[14]="$SRCDIR/x264-$X264.tar.gz"
< SRCURL[14]="$CONTRIBURL/x264-$X264.tar.gz"
---
> SOURCE[14]="$SRCDIR/x264-snapshot-${X264}.tar.bz2"
> SRCURL[14]="ftp://ftp.videolan.org/pub/videolan/x264/snapshots/x264-snapshot-${X264}.tar.bz2"
pedro@darkstar:~/Downloads/slackware/alien_repository/handbrake/build$

But it still doesn't work, HandBrake keeps giving a segmentation error.

WhiteWolf1776 · 04-12-2014, 10:16 AM

Some backups don't run properly with Handbrake, so you may need to use makeMkv as a first step. I've not seen this encode issue from a makeMkv output.

Handbrake being only a transcoder, sometimes it needs better inputs to work from. I use aliens pre-built blob.

moisespedro · 04-12-2014, 11:52 AM

I don't get what you meant. HandBrake always crashes when I try to encode a video using x264, if I switch the encoder to MPEG-4 it runs fine.

Mark Pettit · 04-12-2014, 12:35 PM

I also recommend AlienBobs prebuilt binary. In fact, If there's anything I want and he has it, that's my first port of call. Period. No arguments.

moisespedro · 04-12-2014, 01:23 PM

Quote:

Originally Posted by Mark Pettit

I also recommend AlienBobs prebuilt binary. In fact, If there's anything I want and he has it, that's my first port of call. Period. No arguments.

I used it and still got the segmentation fault, I used his default script.

moisespedro · 04-12-2014, 01:50 PM

Well, I decided to try the prebuilt package and it works. Damn, something might be wrong in my system.

j_v · 04-12-2014, 02:40 PM

Out of curiosity, I tried to test this with the SBo package. Transcoding segfaulted here as well, except if I used the "Placebo" preset. I think you make a good choice to use AlienBOB's prebuilt. I've found that his binaries are quite reliable. I do most of my transcoding using ffmpeg, but have for long been curious about HandBrake. I noted a common error just before segfaults:

Code:

x264 [warning]: --psnr used with psy on: results will be invalid!
x264 [warning]: --tune psnr should be used if attempting to benchmark psnr!

I intend to find the meaning of these errors and figure out what is the cause.

moisespedro · 04-12-2014, 03:32 PM

Quote:

Originally Posted by j_v

Out of curiosity, I tried to test this with the SBo package. Transcoding segfaulted here as well, except if I used the "Placebo" preset. I think you make a good choice to use AlienBOB's prebuilt. I've found that his binaries are quite reliable. I do most of my transcoding using ffmpeg, but have for long been curious about HandBrake. I noted a common error just before segfaults:

Code:

x264 [warning]: --psnr used with psy on: results will be invalid!
x264 [warning]: --tune psnr should be used if attempting to benchmark psnr!

I intend to find the meaning of these errors and figure out what is the cause.

I didn't understand why changing x264 version didn't fix the problem. I also used alien's script with no modifications and the generated binary gave me segmentation faults.

Alien Bob · 04-12-2014, 04:00 PM

Quote:

Originally Posted by moisespedro

I used it and still got the segmentation fault, I used his default script.

Did you install my package or did you use my handbrake.SlackBuild script to produce your own package?

Eric

j_v · 04-12-2014, 04:38 PM

This page references the bug: https://bugs.launchpad.net/ubuntu/+s...4/+bug/1241772. I have tested the added CFLAG on the SBo SlackBuild and it fixes the issue for me. I will get in touch with the maintainer after dinner.

j_v · 04-12-2014, 05:04 PM

Here is a link to the patch:

https://github.com/jvvv/slackbuilds/...segfault.patch

I'll be notifying package maintainer after I post this.

Just adding the usual SLKCFLAGS didn't work. So I saved the current environment for CFLAGS and CXXFLAGS, exported the SLKCFLAGS as CFLAGS and CXXFLAGS, and then restored the saved CFLAGS and CXXFLAGS after compilation completes; this worked for me.

Cheers

moisespedro · 04-12-2014, 05:24 PM

Quote:

Originally Posted by Alien Bob

Did you install my package or did you use my handbrake.SlackBuild script to produce your own package?

Eric

As I said before on the thread:
I tried SBo's stock script
I tried yours stock script
I tried a modified version of your script with a newer x264 tarball

All of them gave me the segmentation error. Now I've installed your prebuilt package and it works fine.

Alien Bob · 04-12-2014, 05:37 PM

Quote:

Originally Posted by moisespedro

As I said before on the thread:
I tried SBo's stock script
I tried yours stock script
I tried a modified version of your script with a newer x264 tarball

All of them gave me the segmentation error. Now I've installed your prebuilt package and it works fine.

My package works fine because it was compiled with gcc-4.7. The bug in x264 is only present when you compile it with gcc-4.8 ...

Eric

moisespedro · 04-12-2014, 05:40 PM

Quote:

Originally Posted by Alien Bob

My package works fine because it was compiled with gcc-4.7. The bug in x264 is only present when you compile it with gcc-4.8 ...

Eric

Well but since someone said this on the bugreport

Quote:

Configure x264 with "--extra-cflags=-fno-aggressive-loop-optimizations" solves this problem.
Also seems that problem solved in trunk - http://git.videolan.org/?p=x264.git;...eb12504711b94f

And the bug report is 6 months old I thought a newer tarball would fix it (I used the latest tarball avaliable)

Alien Bob · 04-12-2014, 05:49 PM

Quote:

Originally Posted by moisespedro

And the bug report is 6 months old I thought a newer tarball would fix it (I used the latest tarball avaliable)

Are you sure the build used that newer tarball? Handbrake downloads a very specific version of x264 which is hardcoded in the build script. All my SlackBuild script does is download it beforehand, so that you can do an offline build of the package.
Check your build log (you kept a log did you?) and find out if a x264 tarball was downloaded before the compilation started.

Eric