Crash processing BD+

The place to discuss linux version of MakeMKV
Post Reply
hifi25nl
Posts: 3
Joined: Thu Mar 22, 2018 2:06 pm

Crash processing BD+

Post by hifi25nl » Fri Mar 23, 2018 2:56 pm

I was trying to save Men in Black 3 Blu Ray (not UHD) and makemkv (last version) crash at processing bd+
Tried with java 8 and java 9 in archlinux, in the log the last line is only
003344:0000 Using Java runtime from /usr/lib/jvm/java-9-openjdk/bin/java

No other clues...
?

hifi25nl
Posts: 3
Joined: Thu Mar 22, 2018 2:06 pm

Re: Crash processing BD+

Post by hifi25nl » Sun Mar 25, 2018 11:17 am

I have also tried oracle java 9, as suggested on another thread, but I have always the crash BD+ decoding.
Strangely, with the same keys installed in makemkv directory, windows version is working fine.

Woodstock
Posts: 5448
Joined: Sun Jul 24, 2011 11:21 pm

Re: Crash processing BD+

Post by Woodstock » Sun Mar 25, 2018 3:38 pm

Normally, MakeMKV does not need Java to process BD+, only for playlist obfuscation.

Are there details from the crash in the system logs?
How to aid in finding the answer to your problem: https://www.makemkv.com/faq/item/8

hifi25nl
Posts: 3
Joined: Thu Mar 22, 2018 2:06 pm

Re: Crash processing BD+

Post by hifi25nl » Sun Mar 25, 2018 9:59 pm

MakeMKV log:

Code: Select all

Debug log started at Sun Mar 25 21:53:27 2018 , written by MakeMKV v1.12.0 linux(x64-release)
Using 1048320KB for read cache.
001005:0000 MakeMKV v1.12.0 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as /home/audiolinux/MakeMKV_log.txt
003007:0000 Using direct disc access mode
DEBUG: Code 2365587456 at >YV#m(}-q[^=M?S2:29402808
DEBUG: Code 2147483648 at >YV#m(}-q[^=M?S2:29396483
DAFD=PAAAADAAAAEABDQkEFwECAQ==
DCE=5MwQFtQUDiKGll0EyPhU0lE7DnA2B0Fd2EWbjpHpRmkPMLpipf3Px1Rt/o5qNa5Liu8bvCDtlQruJG06mvjUg6hBXH0YOIsY8mlnysGjog+9Idi/JOsEZggU9VsIKI5Xeo3+mhtARc1W2idMNj6ws3v5gEJCxGMAag==
DCE=+fY5ofKBVsaQsaJfWl7RiO8lK4fdoqjiRoRY5+AR+NYKk+8KSCMmcsMvpEgXCMjGBRRlbaGmuBPVV45couUC6df8bfB4GCHWfd+Km4OGw3YXIYVz/mTJP8I569ZYDPvauDaBfXVVOJy9k0uizebQmLLHekfDAaeJpg==
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
003344:0000 Using Java runtime from /usr/bin/java
dmesg output:

Code: Select all

[ 3219.548945] makemkvcon[12812]: segfault at 8 ip 000000000060e29d sp 00007f9a47ff8e10 error 4 in makemkvcon[400000+5bf000]
No relevant error from journalctl

Makemkv crashes at /BDMV/PLAYLIST/00003.mpls

ianwestc
Posts: 1
Joined: Fri Apr 27, 2018 10:21 pm

Re: Crash processing BD+

Post by ianwestc » Fri Apr 27, 2018 10:25 pm

hifi25nl wrote: Makemkv crashes at /BDMV/PLAYLIST/00003.mpls
Any luck or progress? Which Blu-Ray were you trying to read?
makemkv crashes consistently and reliably for me while processing /BDMV/PLAYLIST/00003.mpls on the Hacksaw Ridge Blu-Ray. I haven't found another blu-ray yet where this happens.

chill
Posts: 9
Joined: Sat Nov 19, 2011 4:58 pm

Re: Crash processing BD+

Post by chill » Wed May 02, 2018 10:14 pm

This happens to me, also, on a couple different BR discs, though not all of them. Most recently, Looper.

Drive Information
OS device name: /dev/sr0
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE WH10LS30
Revision: 1.00
Serial number: K9VA4OG3137
Firmware date: 2009-11-25 12:34:56
Highest AACS version: 63

Disc Information
Label: LOOPER
Timestamp: 2012-11-07 15:41:03
Data capacity: 45.70 Gb
Disc type: BD-ROM
Number of layers: 2
Channel bit length: 74,5 nm (25.0 GB max. per layer)

Debug log started at Wed May 2 22:07:40 2018 , written by MakeMKV v1.12.2 linux(x64-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.12.2 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as /home/chill/MakeMKV_log.txt
001003:0020 DEBUG: Code 0 at ML*0.;a7O|%,nkjVO-(fcLv:213130122
003007:0000 Using direct disc access mode
DEBUG: Code 2365587456 at 5OtQOT?(`ld'gHMk:121271065
DEBUG: Code 2147483648 at 5OtQOT?(`ld'gHMk:29396483
DAFD=PAAAADAAAAEABDQUEAQEBAQ==
DCE=kEkeRm4C8lJ4zVJf0UuLKi0datBe8+J1R1F7mP9cYeGkyggiujyTxjvbIQrq6QF4Li67EVxRseamOmsObZK7dUHsMaRxD9tQ3ZyAAT0iY+PNRvczOnkexY0cnZFg0erg6R54Vtb7nmW5tYN9OtWyvqEKxjJF232yxw==
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
Found java version=1.8.0.162 path=/usr/lib/jvm/java-8-openjdk-amd64/bin/java
Found java version=1.8.0.162 path=/usr/bin/java
003344:0000 Using Java runtime from /usr/lib/jvm/java-8-openjdk-amd64/bin/java

It then crashes on reading /BDMV/PLAYLIST/00003.mpls displaying a dialog that says "Fatal error occurred, program will now exit." and closes.

My DMESG log (Ubuntu 17.10.1, x86_64) shows:

[40584.422562] makemkvcon[784]: segfault at 8 ip 000000000060e45d sp 00007f109b3fcca0 error 4 in makemkvcon[400000+5c2000]

chill
Posts: 9
Joined: Sat Nov 19, 2011 4:58 pm

Re: Crash processing BD+

Post by chill » Wed May 23, 2018 7:19 pm

This is a Java issue, as it is java that segfaults. I installed Oracle Java 10 and this problem went away.

ksquared
Posts: 2
Joined: Sat Jun 02, 2018 8:32 pm

Re: Crash processing BD+

Post by ksquared » Sat Jun 02, 2018 9:12 pm

I just went through updating Java from 8u121 -> 8u171 -> 10.0.1 with MakeMKV 1.12.0 and 1.12.2 on Ubuntu 16.04 LTS (up-to-date) and I still get a crash very similar to what was mentioned before. Disc is BR "Just Getting Started". Logs are below.

This is the first time I've ever experienced a segfault with MakeMKV on my system. Any more ideas I could try?

Thanks,
K^2

From dmesg:
[2934518.035723] makemkvcon[24113]: segfault at 8 ip 000000000060e45d sp 00007f1293ff8e40 error 4 in makemkvcon[400000+5c2000]

From MakeMKV_log.txt:
Debug log started at Sat Jun 2 20:54:22 2018 , written by MakeMKV v1.12.2 linux(x64-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.12.2 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as /home/key/MakeMKV_log.txt
001003:0020 DEBUG: Code 0 at ML*0.;a7O|%,nkjVO-(fcLv:213130122
003007:0000 Using direct disc access mode
DEBUG: Code 2365587456 at 5OtQOT?(`ld'gHMk:121271065
DEBUG: Code 2147483648 at 5OtQOT?(`ld'gHMk:29396483
DAFD=PAAAADAAAAEABDQkEHgACAQ==
DCE=QrfgVkX+Ol+lwXQ1+pkfBknOFFME09TftTELnatu+zLFcntzY3uPSxmH7peE/uRanOgbr+EbpaVM6aCGXwtHUlD48qLNOInlVkbJfUDafjytS/mwECdn4Yi2HwOte4EQKogMPsY9XgPUJpQ3vb9AhbKF7GWGiE47dw==
DCE=p9lV07e4zAFfuvgouQxkC+oJYJqWXCL/Tnqt5oeyp3x1h6EJxLz4KCYDFkk96PQ4eAqp/jRUdyHKiJZFDLRLJ2wv33PuH7oQECjz7GOM4IStBP+udDOPgShPbre1YW6PX+u4Fk43PDdyjFtUKkrt+5cVEipOXZPfcw==
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
003344:0000 Using Java runtime from /usr/lib/jvm/java-10-oracle/bin/java

ksquared
Posts: 2
Joined: Sat Jun 02, 2018 8:32 pm

Re: Crash processing BD+

Post by ksquared » Sat Jun 02, 2018 11:25 pm

FYI, I cannibalized a Pioneer BDR-206 from an old machine and put it into a Vantec USB 2.0 (yikes!) enclosure. MakeMKV seems happy with the same disc on my Mac. I'll check my calendar for when it will finish...

bmillham
Posts: 19
Joined: Mon Mar 27, 2017 12:42 am

Re: Crash processing BD+

Post by bmillham » Sun Aug 26, 2018 2:06 am

I just ran into this problem again with the UHD version of Wonder. I was able to get around it (on linux) by:

sudo mv /usr/lib/jvm /usr/lib/jvm.save

That way MakeMKV couldn't find the Java runtime and I was able to rip the disc (at least it's in progress).
Once it's done I can just rename the directory again to re-enable Java. I'm running the latest Oracle version btw.

karen7
Posts: 1
Joined: Thu Sep 06, 2018 5:03 pm

Re: Crash processing BD+

Post by karen7 » Thu Sep 06, 2018 5:25 pm

I'm having the same issue on Linux mint 18.2 Sonya (Ubuntu 16.04). I was processing the Breaking Bad series 4 disk 1 when makeMKV stopped with a fatal error and said it had to exit. Accordingly a segmentation fault as others mentioned above. Here are my details...

From demsg:

[7998784.721180] makemkvcon[31741]: segfault at 8 ip 000000000060c65d sp 00007f8a53f8fe30 error 4 in makemkvcon[400000+5db000]

And from the log:

Debug log started at Thu Sep 6 03:53:34 2018 , written by MakeMKV v1.12.3 linux(x64-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.12.3 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as /home/karen/MakeMKV_log.txt
001003:0020 DEBUG: Code 0 at jBhtu(/G*)T_Fd{m)U=fI{7:213130122
003007:0000 Using direct disc access mode
DEBUG: Code 2365587456 at t~d-p%G)tJaZNt$C:29405660
DEBUG: Code 0 at t~d-p%G)tJaZNt$C:213139943
DEBUG: Code 0 at Zl.(dKCx3Nt;JVo&:29400623
DEBUG: Code 2147483648 at t~d-p%G)tJaZNt$C:213133250
DAFD=PAAAADAAAAEABDQkEHgACAQ==
DCE=1CfEfDxtZ67P/C9I2lD0DQFr9A03/jDcdMfOyMWljCv66o+vbecW0ssQFYKNomi+rXH59NcqzTP1vBsfxgGwfUT5NAs0RwmFImRUgQn5//nfZ7nBA33p
m469KD796Bq70RuNu+RIcFMGf98vE6cJKZu2rYikMYQW0Q==
DCE=Cu+xjX0SIU+0hLhWwTryZUmW0lw108tHd8NDOC7GP0uMca7oq2b+ZZgOLonB4dRqs3/pnf6fPHy+yCdxidrz18bP8VI7FtFF2nlBIQCthTc0IqK2YdxI
xJpTDdHmeYStZPSDxq7PuOcYx44s3bLEvQC1WMiD9BEwGA==
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
Found java version=1.8.0.181 path=/usr/lib/jvm/java-8-openjdk-amd64/bin/java
Found java version=1.8.0.181 path=/usr/bin/java
003344:0000 Using Java runtime from /usr/lib/jvm/java-8-openjdk-amd64/bin/java

The main window indicates that it was parsing the file /BDMV/PLAYLIST/00003.mpls
There do not appear to be any more messages, it ends with "Using java runtime from /usr/lib/jvm/java-8-openjdk-amd64/bin/java

Please ping me if I can provide any additional information or logs.
Thanks!

Post Reply