ffmpeg with x265 crashes on OpenVZ and Ubuntu on Windows

[Jason Duerstock]

I'm having trouble collecting more debug info for various reasons, but I'm getting the following final bits with strace:

open("/sys/devices/system/node/node0/cpumap", O_RDONLY) = -1 ENOENT (No such file or directory)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x402268da8} ---
+++ killed by SIGSEGV +++
Segmentation fault

Is there a way to manually analyze a core file with apport?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ffmpeg 7:2.8.6-1ubuntu2
Uname: Linux 2.6.32-042stab113.21 x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Aug 5 09:14:01 2016
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ffmpeg
UpgradeStatus: Upgraded to xenial on 2016-03-16 (141 days ago)

[Carl Eugen Hoyos (cehoyos)]

Sorry if I miss something:
If you see a crash with ffmpeg, please provide both the command line that you tested and the complete, uncut console output. If you cannot provide the intput file that allows to reproduce the issue, please provide backtrace, disassembly and register dump as explained on https://ffmpeg.org/bugreports.html
If the crash is only reproducible with -vcodec libx265, there is a possibility that the issue is not FFmpeg-related.

[Jason Duerstock (evilmoo)]

I think you're correct -- this is most likely a libx265 bug. How do I change this bug to point to libx265 rather than ffmpeg?

[Carl Eugen Hoyos (cehoyos)]

Affected package is probably libx265

[Launchpad Janitor (janitor)]

[Expired for x265 (Ubuntu) because there has been no activity for 60 days.]