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 »

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 »

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: 8386
Joined: Sun Jul 24, 2011 11:21 pm

Re: Crash processing BD+

Post by Woodstock »

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

Are there details from the crash in the system logs?
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
hifi25nl
Posts: 3
Joined: Thu Mar 22, 2018 2:06 pm

Re: Crash processing BD+

Post by hifi25nl »

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 »

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 »

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 »

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 »

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 »

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: 99
Joined: Mon Mar 27, 2017 12:42 am

Re: Crash processing BD+

Post by bmillham »

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 »

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!
penguinmeister
Posts: 2
Joined: Thu Jul 13, 2017 10:02 am

Re: Crash processing BD+

Post by penguinmeister »

Same problem with Men in Black 3 on Linux. I'm running Devuan ACSII which is based on Debian 9 ("Stretch").

I'm running the latest 1.14.5 release of MakeMKV. The log says:

Debug log started at Mon Sep 9 11:25:08 2019 , written by MakeMKV v1.14.5 linux(x64-release)
Using 262272KB for read cache.
001005:0000 MakeMKV v1.14.5 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as /home/roger/MakeMKV_log.txt
001003:0020 DEBUG: Code 0 at 8Z9')"E=^}]^lh_bh52\.=*:213130122
SDF v05f: HL-DT-ST_BD-RE__BH16NS40_1.01_211304042250_K9LD7QC0937
003007:0000 Using direct disc access mode
SDF v05f: HL-DT-ST_BD-RE__BH16NS40_1.01_211304042250_K9LD7QC0937
001011:0000 LibreDrive firmware support is not yet available for this drive (id=A2C5551650D3)
DEBUG: Code 2317353437 at lH]X/?PO~dv$@a$Ac:121264096
DEBUG: Code 0 at lH]X/?PO~dv$@a$Ac:121264119
DEBUG: Code 2317353437 at lH]X/?PO~dv$@a$Ac:121264096
DEBUG: Code 1 at lH]X/?PO~dv$@a$Ac:121264119
DEBUG: Code 2317353437 at lH]X/?PO~dv$@a$Ac:121264096
DEBUG: Code 2 at lH]X/?PO~dv$@a$Ac:121264119
DEBUG: Code 2317353437 at lH]X/?PO~dv$@a$Ac:121264096
DEBUG: Code 3 at lH]X/?PO~dv$@a$Ac:121264119
DEBUG: Code 2317353437 at lH]X/?PO~dv$@a$Ac:121264096
DEBUG: Code 4 at lH]X/?PO~dv$@a$Ac:121264119
DEBUG: Code 2317353437 at lH]X/?PO~dv$@a$Ac:121264096
DEBUG: Code 5 at lH]X/?PO~dv$@a$Ac:121264119
DEBUG: Code 2317353437 at lH]X/?PO~dv$@a$Ac:213132652
DEBUG: Code 0 at X])n#SpGfac$1n69:213141530
DEBUG: Code 0 at NK#"t]-b?7QNQvv6:29400669
DEBUG: Code 2147483648 at X])n#SpGfac$1n69:213132974
DAFD=PAAAADAAAAEABDQkEFwECAQ==
DCE=NgTV9AQVFn/CiOu99cGJXg+F/yS7MepnW7moJQHo6o8HzxPYGRjgYq5m1qntEZcb8hOszCXFloT02db3cevkDFmdJmyEm/IYYGrCN2w7pReMIb/l5kY+lEtx64e/3Ma2j+g7Fu4P/6nv1y7z9y4X0bma4ZfixEKnLw==
DCE=vb29vb1a/apeimdnE7AgbdLgbjvy6dNTaCljwQ0Al2MCuuUYm189c1wfvw+SvXSafBmu082akJaKBAalfpg977ZZWtG9JagXaazZUy1y6iXLilaJ3jKDcMfrGW8KZnzUZ/65ULAI1/M71cG76Lh5T3F/u7ZEsiDirw==
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
Found java version=1.8.0.222 path=/usr/lib/jvm/java-8-openjdk-amd64/bin/java
Found java version=1.8.0.222 path=/usr/bin/java
003344:0000 Using Java runtime from /usr/lib/jvm/java-8-openjdk-amd64/bin/java

My workaround was to go to "View" -> "Preferences", select the "Protection" tab and then change the "Custom Java executable location" to "/bin/true". This doesn't run Java.

With this change, I was able to successfully rip the main ~23GB file and it plays OK. I assume that Java *is* required for some functionality, however, so I'm not sure what this change breaks.

I've emailed support with the disk information as per https://www.makemkv.com/faq/item/8
cpu2910
Posts: 1
Joined: Fri Sep 17, 2021 2:52 pm

Re: Crash processing BD+

Post by cpu2910 »

Years gone by....
I've never had any problems with makemkv, no for the first time and found this forum entry.

For me changing the Java Custom executable to '/bin/true' does work...

The Disc was 'The perfect getaway (2009)'.
kevmitch
Posts: 72
Joined: Mon Mar 11, 2013 6:35 am

Re: Crash processing BD+

Post by kevmitch »

Most discs work fine including 4k, blu ray, dvd. However I'm segfaulting with with Indiana Jones and the Last Crusade 4k

Code: Select all

    "Type": "Blu-ray disc",
    "Name": "Indiana Jones and the Last Crusade",
    "MetadataLanguageCode": "eng",
    "MetadataLanguageName": "English",
    "TreeInfo": "Indiana Jones and the Last Crusade",
    "PanelTitle": "<b>Source information</b><br>",
    "VolumeName": "INDIANAJONES_LAST_CRUSADE",
    "OrderWeight": 0,
    "Comment": "",
and the Lord of the Rings: The Return of the King 4k

Code: Select all

    "Type": "Blu-ray disc",
    "Name": "The Lord of the Rings: The Return of the King (EXT.) PT. 2",
    "MetadataLanguageCode": "eng",
    "MetadataLanguageName": "English",
    "TreeInfo": "The Lord of the Rings: The Return of the King (EXT.) PT. 2",
    "PanelTitle": "<b>Source information</b><br>",
    "VolumeName": "LOTR_THE_RETURN_OF_THE_KING_P2",
    "OrderWeight": 0,
    "Comment": "UHD-135447_LoTR_RotK_EE_P2_UHD01_DIM2",
It doesn't seem to matter what jre I use. java-8 (jre1.8.0_301) , oracle java-10 (jre-10.0.2), openjdk-8 - openjdk-18 they all segfault when trying to scan the disc. There are rare instances where it doesn't, which is where I got the above disc data. The only thing that reliably doesn't segfault is if I remove all jres, but then I lose all the "Comments" which helpfully indicate "MainFeature" etc.

The below is from LOTR: ROK 4k:

Code: Select all

$ gdb --args makemkvcon --noscan  -r info dev:/dev/sr0 
GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
...
Reading symbols from makemkvcon...
(No debugging symbols found in makemkvcon)
(gdb) run
Starting program: /usr/bin/makemkvcon --noscan -r info dev:/dev/sr0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef4f5640 (LWP 2779)]
MSG:1005,0,1,"MakeMKV v1.16.4 linux(x64-release) started","%1 started","MakeMKV v1.16.4 linux(x64-release)"
MSG:1004,131072,1,"Debug logging enabled, log will be saved as file:///home/kevmitch/MakeMKV_log.txt","Debug logging enabled, log will be saved as %1","file:///home/kevmitch/MakeMKV_log.txt"
[New Thread 0x7fffeec13640 (LWP 2780)]
[New Thread 0x7fffd5a1c640 (LWP 2781)]
MSG:1003,32,3,"DEBUG: Code 0 at :dF09'kc`L+X+;OGG >t^*:29393631","DEBUG: Code %1 at %2:%3","0",":dF09'kc`L+X+;OGG >t^*","29393631"
DRV:0,0,999,0,"BD-RE HL-DT-ST BD-RE  WH16NS60 1.02","","/dev/sr0"
DRV:1,0,999,0,"BD-RE ATAPI iHBS212   2 53T1","","/dev/sr1"
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:1011,0,1,"Using LibreDrive mode (v06.2 id=7FA2657C7667)","%1","Using LibreDrive mode (v06.2 id=7FA2657C7667)"
MSG:3007,0,0,"Using direct disc access mode","Using direct disc access mode"
MSG:5085,0,0,"Loaded content hash table, will verify integrity of M2TS files.","Loaded content hash table, will verify integrity of M2TS files."
[Detaching after vfork from child process 2782]
[Detaching after vfork from child process 2798]
[Detaching after vfork from child process 2814]
MSG:3344,0,1,"Using Java runtime from /usr/lib/jvm/java-11-openjdk-amd64/bin/java","Using Java runtime from %1","/usr/lib/jvm/java-11-openjdk-amd64/bin/java"

Thread 2 "makemkvcon" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffef4f5640 (LWP 2779)]
0x00000000007acb8b in ?? ()
(gdb) bt
#0  0x00000000007acb8b in  ()
#1  0x00000000007ac575 in  ()
#2  0x00000000007ac485 in  ()
#3  0x00000000007b8d41 in  ()
#4  0x00000000007b8f19 in  ()
#5  0x00000000007b7cf1 in  ()
#6  0x00000000006d0883 in  ()
#7  0x00000000006cbaf2 in  ()
#8  0x00000000006d1124 in  ()
#9  0x00000000007f2a83 in  ()
#10 0x00000000007f1329 in  ()
#11 0x00000000007f4224 in  ()
#12 0x000000000065aff1 in  ()
#13 0x000000000065be44 in  ()
#14 0x00007ffff7eedeae in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0
#15 0x00007ffff7e1da5f in clone () at /lib/x86_64-linux-gnu/libc.so.6
(I installed the openjdk-11-dbg package, but I guess it doesn't look there if makemkvcon doesn't have debug symbols itself.)

Debug log:

Code: Select all

$ cat $HOME/MakeMKV_log.txt 
Debug log started at Thu Sep 23 10:49:58 2021 , written by MakeMKV v1.16.4 linux(x64-release)
001005:0000 MakeMKV v1.16.4 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///home/kevmitch/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.74.0/OpenSSL/1.1.1l/1.43.0 (x86_64-pc-linux-gnu) , proxy server not set.
001003:0020 DEBUG: Code 0 at :dF09'kc`L+X+;OGG >t^*:29393631
SDF  v07e: HL-DT-ST_BD-RE__WH16NS60_1.02_211810291936_KLDKBPA1352
No  SDF v07e: ATAPI_iHBS212___2_53T1_3772512013_216040503511
SDF id v07e: ATAPI_iHBS212___2_53T1_3772512013_216040503511
SDF  v07e: HL-DT-ST_BD-RE__WH16NS60_1.02_211810291936_KLDKBPA1352
001011:0000 Using LibreDrive mode (v06.2 id=7FA2657C7667)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at <_zSP&06Pi+Hb)S):121264625
Found java version=11.0.12 path=/usr/lib/jvm/java-11-openjdk-amd64/bin/java
Found java version=11.0.12 path=/usr/bin/java
Found java version=11.0.12 path=/bin/java
Found java version=10.0.2 path=/home/kevmitch/.MakeMKV/jre-10.0.2/bin/java
003344:0000 Using Java runtime from /usr/lib/jvm/java-11-openjdk-amd64/bin/java
Post Reply