sbraz/pymediainfo

Segmentation Fault

apiszcz opened this issue · 8 comments

Calling parse on some files is causing a segmentation fault and the python VM exits. Is there an approach to mitigate this unexpected exit? Perhaps a .verify method?
Thank you for the API.

Perhaps .can_parse is the option, will test.

sbraz commented

Hi, can you please attach one of these files? Does mediainfo also fail to parse them? What version of the library are you using?

Hi, unfortunately not, i will see how can_parse does with the next file i encounter that causes a segmentation fault.

sbraz commented

can_parse just checks that the library is usable. It does not take media files into account. Did you also check my other suggestions (try with the CLI, check the version of libmediainfo)?

The CLI (separate test on a different windows computer)
MediaInfo Command line,
MediaInfoLib - v22.06
Processes and displays the information for the file successfully.

The version on Ubuntu / Linux system where the issue occurs
libmediainfo-dev/focal,now 19.09+dfsg-2build1 amd64 [installed]
libmediainfo0v5/focal,now 19.09+dfsg-2build1 amd64 [installed,automatic]

FYI
libmediainfo-dev is already the newest version (19.09+dfsg-2build1).

The file also plays / displays properly with 'mpv'.
VLC is unable to play/display the file.

sbraz commented

The version on Ubuntu / Linux system where the issue occurs

Can you please install the CLI mediainfo on it and see if it works? Also please try the version from the MediaInfo repositories: https://mediaarea.net/en/Repos

Will do, testing next.
libmediainfo-dev/focal 22.06-1 amd64 [upgradable from: 19.09+dfsg-2build1]
libmediainfo-doc/focal 22.06-1 all
libmediainfo0v5-dbg/focal 22.06-1 amd64
libmediainfo0v5/focal 22.06-1 amd64 [upgradable from: 19.09+dfsg-2build1]
mediainfo-dbg/focal 22.06-1 amd64
mediainfo-gui-dbg/focal 22.06-1 amd64
mediainfo-gui/focal 22.06-1 amd64
mediainfo/focal 22.06-1 amd64

NO similar issues yet, thank you.

sbraz commented

@apiszcz so the upgrade made pymediainfo work with the file with which it failed before? If so, I assume we can close this issue.