Segmentation fault

[GoogleCodeExporter]

$ ./7-7-13/build/vpxenc --codec=vp9 -o out9.webm scaled9.y4m 

gives 

Pass 1/1 frame    2/1       1298B 8196608 us 4098.30 ms/f [ETA  0:33:44] 
Segmentation fault (core dumped)

on Ubuntu 12.04. I've downloaded the most recent version of the code using git.

Original issue reported on code.google.com by jerm...@gmail.com on 7 Jul 2013 at 8:03

[GoogleCodeExporter]

Is this even the official bug tracker? I got no response the last two weeks.

on topic:
--codec=vp8 works 
(It is only vp9 which crashes)

Original comment by jerm...@gmail.com on 19 Jul 2013 at 2:19

[GoogleCodeExporter]

Do you still see this behavior with the current libvpx tip? vpxenc/VP9 should 
be considered unstable.

Original comment by louquil...@google.com on 24 Jul 2013 at 11:10

[GoogleCodeExporter]

Original comment by louquil...@google.com on 25 Jul 2013 at 6:05

[GoogleCodeExporter]

I can still reproduce the behavior with the current version from 
http://git.chromium.org/webm/libvpx.git . It should be noted that this always 
worked before. However, after the vp9 bitstream has been finalized, the vpxenc 
crashed since then.

So what do you mean by "should be considered unstable"? Is the vpxenc 
deprecated and not developed further?

And: To test the libvpx I need to install ffmpeg or similar?

Original comment by jerm...@gmail.com on 25 Jul 2013 at 7:31

[GoogleCodeExporter]

Tip is unstable because it's under heavy development. There's no deprecation.

I'm not able to duplicate the segfault with a vpxenc built today (commit 
242157c75) on 12.04, using this input:

http://media.xiph.org/video/derf/y4m/akiyo_qcif.y4m

Encode completes without issue. Please test under the same conditions, and 
perhaps make your input file available. Thanks.

Original comment by louquil...@google.com on 25 Jul 2013 at 7:46

• Changed state: Unconfirmed

[GoogleCodeExporter]

I used $ git clone http://git.chromium.org/webm/libvpx.git to get the latest 
version. Also I tried your sample video... Both had no effect.

Maybe my laptop is "too old". Is there any way to have a look at the dump and 
investigate where the problem occurs?

Original comment by jerm...@gmail.com on 26 Jul 2013 at 12:56

[GoogleCodeExporter]

Suggest floating this issue on freenode/#vp8

Original comment by louquil...@google.com on 26 Jul 2013 at 6:54

[GoogleCodeExporter]

(same behavior with ubuntu 12.04.2 live usb image.)

Original comment by jerm...@gmail.com on 26 Jul 2013 at 11:29

[GoogleCodeExporter]

You're not specifying any commandline options, and you're not specifying a 
bitrate. Try options as recommended on relevant recent posts on doom9 or in the 
webm encoding guide (section 10). Something like this should work:

./vpxenc --passes=2  --good --cpu-used=0 --target-bitrate=XYZ --end-usage=vbr \
  --auto-alt-ref=1 \
  --minsection-pct=5--maxsection-pct=800 --lag-in-frames=25 \
  --kf-min-dist=0 --kf-max-dist=360 \
  --min-q=0 --max-q=63 \
  --arnr-maxframes=5 --arnr-strength=3 file.y4m -o video.webm

Original comment by rbul...@google.com on 26 Jul 2013 at 2:42

[GoogleCodeExporter]

Thanks for the feedback. Indeed this was the problem.
However it is weired because it worked previously. What about implementing an 
error message (requesting command line options) instead of the segmentation 
fault?

Original comment by jerm...@gmail.com on 26 Jul 2013 at 4:22

[GoogleCodeExporter]

Closing for now. CLI output for vpxenc --codec=vp9 will be improved for the 
stable release.

Original comment by louquil...@google.com on 13 Aug 2013 at 9:31

• Changed state: WontFix