OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

Originally Posted by nyplayer

What does this do.??
upload_id_enabled=true


Setting it to true improved the response of my Android miniclient... Also improved my livetv channel changes on the miniclient.

It uses the Media Server built into SageTV instead of writing the file directly. I may now have too many checks in the direct file writing which are slowing it down. They were pretty much a reaction to someone having unexplained issues.


Edit: If you want to confirm that's the all of the checking that's causing the issue, try changing consumer.ffmpeg.min_direct_flush_size to -1.

[nyplayer]

Originally Posted by EnterNoEscape

It uses the Media Server built into SageTV instead of writing the file directly. I may now have too many checks in the direct file writing which are slowing it down. They were pretty much a reaction to someone having unexplained issues.


Edit: If you want to confirm that's the all of the checking that's causing the issue, try changing consumer.ffmpeg.min_direct_flush_size to -1.

Much better does this disable all the extra checks I never really needed them.

[EnterNoEscape]

Originally Posted by nyplayer

Much better does this disable all the extra checks I never really needed them.

Yes. That disabled all of the checks. I might just remove them completely since they have yet to show anything interesting for anyone.

[mwittl]

I installed the 4.48 version on a separate PC from my Sage box. Got everything running OK from the DCT box and Sage. Tuners added, working but trying to view anything produces a java write error. I have networking permissions set from the DCT box to Sage and mapped drives from the DCT box to the Sage box. I can manually write files from the DCT box to the Sage box; however, I get the following error when I try to watch or record anything:

INFO   | jvm 1    | 2016/05/01 07:25:29.252 | 07:25:29.252 [SageTVRequestHandler-94:DCT-HDHomeRun Prime Tuner 13215AFE-1] INFO  HDHRNativeCaptureDevice - Configuring and starting the new SageTV consumer...
INFO   | jvm 1    | 2016/05/01 07:25:29.252 | 07:25:29.252 [SageTVRequestHandler-94:DCT-HDHomeRun Prime Tuner 13215AFE-1] ERROR FFmpegTransSageTVConsumerImpl - Unable to open 'I:\SageTV\SesameStreet-BabyBearisAfraidofBees-11161189-0.ts' for writing => java.nio.file.NoSuchFileException: I:\SageTV\SesameStreet-BabyBearisAfraidofBees-11161189-0.ts
INFO   | jvm 1    | 2016/05/01 07:25:29.252 |   at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at sun.nio.fs.WindowsFileSystemProvider.newFileChannel(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at java.nio.channels.FileChannel.open(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at java.nio.channels.FileChannel.open(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at opendct.consumer.FFmpegTransSageTVConsumerImpl$FFmpegDirectWriter.<init>(FFmpegTransSageTVConsumerImpl.java:479)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at opendct.consumer.FFmpegTransSageTVConsumerImpl.consumeToFilename(FFmpegTransSageTVConsumerImpl.java:236)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:971)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:510)
INFO   | jvm 1    | 2016/05/01 07:25:29.283 |   at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:461)
INFO   | jvm 1    | 2016/05/01 07:25:29.283 |   at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:230)
INFO   | jvm 1    | 2016/05/01 07:25:29.283 |   at java.lang.Thread.run(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.283 |
INFO   | jvm 1    | 2016/05/01 07:25:29.283 | 07:25:29.252 [SageTVRequestHandler-94:DCT-HDHomeRun Prime Tuner 13215AFE-1] ERROR SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13215AFE-1 Digital TV Tuner|1206294943|004|2924203866806|I:\SageTV\SesameStreet-BabyBearisAfraidofBees-11161189-0.ts|Great', Replied: 'ERROR Device Start Failed'
INFO   | jvm 1    | 2016/05/01 07:25:29.283 | 07:25:29.252 [SageTVRequestHandler-94:DCT-HDHomeRun Prime Tuner 13215AFE-1] ERROR SageTVRequestHandler - Encoder device is unable to start.
INFO   | jvm 1    | 2016/05/01 07:25:35.205 | 07:25:35.158 [PacketsMonitor-102:NIORTPProducerImpl-99:DCT-HDHomeRun Prime Tuner 13215AFE-1] INFO  NIORTPProducerImpl - Received first 1761 datagram packets. Missed RTP packets 0. Bad RTP packets 0.

Anybody have any thoughts?

[EnterNoEscape]

Originally Posted by mwittl

I installed the 4.48 version on a separate PC from my Sage box. Got everything running OK from the DCT box and Sage. Tuners added, working but trying to view anything produces a java write error. I have networking permissions set from the DCT box to Sage and mapped drives from the DCT box to the Sage box. I can manually write files from the DCT box to the Sage box; however, I get the following error when I try to watch or record anything:

INFO   | jvm 1    | 2016/05/01 07:25:29.252 | 07:25:29.252 [SageTVRequestHandler-94:DCT-HDHomeRun Prime Tuner 13215AFE-1] INFO  HDHRNativeCaptureDevice - Configuring and starting the new SageTV consumer...
INFO   | jvm 1    | 2016/05/01 07:25:29.252 | 07:25:29.252 [SageTVRequestHandler-94:DCT-HDHomeRun Prime Tuner 13215AFE-1] ERROR FFmpegTransSageTVConsumerImpl - Unable to open 'I:\SageTV\SesameStreet-BabyBearisAfraidofBees-11161189-0.ts' for writing => java.nio.file.NoSuchFileException: I:\SageTV\SesameStreet-BabyBearisAfraidofBees-11161189-0.ts
INFO   | jvm 1    | 2016/05/01 07:25:29.252 |   at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at sun.nio.fs.WindowsFileSystemProvider.newFileChannel(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at java.nio.channels.FileChannel.open(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at java.nio.channels.FileChannel.open(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at opendct.consumer.FFmpegTransSageTVConsumerImpl$FFmpegDirectWriter.<init>(FFmpegTransSageTVConsumerImpl.java:479)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at opendct.consumer.FFmpegTransSageTVConsumerImpl.consumeToFilename(FFmpegTransSageTVConsumerImpl.java:236)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:971)
INFO   | jvm 1    | 2016/05/01 07:25:29.267 |   at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:510)
INFO   | jvm 1    | 2016/05/01 07:25:29.283 |   at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:461)
INFO   | jvm 1    | 2016/05/01 07:25:29.283 |   at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:230)
INFO   | jvm 1    | 2016/05/01 07:25:29.283 |   at java.lang.Thread.run(Unknown Source)
INFO   | jvm 1    | 2016/05/01 07:25:29.283 |
INFO   | jvm 1    | 2016/05/01 07:25:29.283 | 07:25:29.252 [SageTVRequestHandler-94:DCT-HDHomeRun Prime Tuner 13215AFE-1] ERROR SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13215AFE-1 Digital TV Tuner|1206294943|004|2924203866806|I:\SageTV\SesameStreet-BabyBearisAfraidofBees-11161189-0.ts|Great', Replied: 'ERROR Device Start Failed'
INFO   | jvm 1    | 2016/05/01 07:25:29.283 | 07:25:29.252 [SageTVRequestHandler-94:DCT-HDHomeRun Prime Tuner 13215AFE-1] ERROR SageTVRequestHandler - Encoder device is unable to start.
INFO   | jvm 1    | 2016/05/01 07:25:35.205 | 07:25:35.158 [PacketsMonitor-102:NIORTPProducerImpl-99:DCT-HDHomeRun Prime Tuner 13215AFE-1] INFO  NIORTPProducerImpl - Received first 1761 datagram packets. Missed RTP packets 0. Bad RTP packets 0.

Anybody have any thoughts?

If the I: drive is a mapped drive, it may be a lot of hassle to get it working like that. Mapped drives are per user and even per context. The OpenDCT service by default uses the local system account which will definitely not see your mapped drive. You will have a far easier time using the UNC path instead. (Ex. \\servername\share)

You can try the advice from this post, but since it will be running as administrator, it likely will still not see your mapped drive.

To demonstrate what I'm talking about click on Start, then type cmd. Right-click on cmd.exe, then click Run as Administrator. Now type in "I:" without the quotes and press Enter. If you don't see a message like "The system cannot find the drive specified.," Then you likely have disabled UAC, but also that means that if you follow the directions in the post mentioned in the previous paragraph, it should work.

At that elevated command prompt, you can still map your I: drive if you want with the following command:

NET USE /PERSISTENT:YES I: \\servername\share

If at some point you want to remove that share, you'll need to run the following also on an elevated command prompt:

NET USE /DELETE I:

If the I: drive is not being shared at the root of the hard drive you're using for recording you will also have issues recording. If all else fails or you don't want to deal with paths and permission issues, you can also do the following:

1) Stop the OpenDCT service.
2) Open C:\ProgramData\OpenDCT\config\opendct.properties
3) Change the values of consumer.ffmpeg.upload_id_enabled and
consumer.raw.upload_id_enabled to true.
4) Start the OpenDCT service.

Those steps will enable to use of the Media Server built into SageTV which basically will completely bypass any security/mapping related issues. The only downside is that it adds to the load on your SageTV server which may or may not be a problem.

[CptKirk]

Was gone this weekend. Came back to an unhappy wife

Had quite a few 'Halt Detected in Recording' messages. Looking at the logs seems like there were some on 4/25. Then a bunch on 4/30, 5/1 and 5/2.

I've attached all the logs. Maybe they can help.

Would changing over to Beta 0.5.x help at all?

Thanks

[EnterNoEscape]

Originally Posted by CptKirk

Was gone this weekend. Came back to an unhappy wife

Had quite a few 'Halt Detected in Recording' messages. Looking at the logs seems like there were some on 4/25. Then a bunch on 4/30, 5/1 and 5/2.

I've attached all the logs. Maybe they can help.

Would changing over to Beta 0.5.x help at all?

Thanks

It might, but based on what appears to be the root cause of your issues (networking), I doubt it. That being said, it won't hurt.

[CptKirk]

I'll change some easy things before I go start buying new hardware.

1. Moved the HDHR from my upstairs work area switch downstairs to the switch that the SageTV server is connected to.
2. Replaced the SiliconDust supplied Cat 5e cable with a Cat 6 cable.

If I still see problems I'll then change out the network card and/or the switch.

[jgsouthard]

Originally Posted by CptKirk

I'll change some easy things before I go start buying new hardware.

1. Moved the HDHR from my upstairs work area switch downstairs to the switch that the SageTV server is connected to.
2. Replaced the SiliconDust supplied Cat 5e cable with a Cat 6 cable.

If I still see problems I'll then change out the network card and/or the switch.

You might try running the network packet loss test that is built into the HDHomeRun products. Instructions are at https://www.silicondust.com/forum/viewtopic.php?t=5877, along with some other things to check regarding network issues.

At the beginning of my nightmare period with SageTV halt errors (which ultimately led me to switch to OpenDCT), I found that I was getting some packet loss from the Motherboard NIC in my SageTV PC (switched to a discrete Intel NIC).

[EnterNoEscape]

Originally Posted by CptKirk

I'll change some easy things before I go start buying new hardware.

1. Moved the HDHR from my upstairs work area switch downstairs to the switch that the SageTV server is connected to.
2. Replaced the SiliconDust supplied Cat 5e cable with a Cat 6 cable.

If I still see problems I'll then change out the network card and/or the switch.

Sounds like a good plan. I hate networking issues; I hate spending money on them blindly even more. Last year I bought two 48 port gigabit, 2 port 10 gigabit enterprise class switches to replace two 8 port D-Link switches and I have to say the difference is more dramatic than I expected. I was blaming a lot of things on my NIC, but it turns out that wasn't the real issue.

[nyplayer]

This is a great tool to check the speed to your network when writing files.

http://totusoft.com/lanspeed/


I also disabled all offloads on my NIC and reran the lanspeed test and it increased dramatically.... also disable Interrupt Moderation.

I simply used a pc client that is on the same switch as my Sage Server and wrote large files .... before disabling the above and after disabling the above. Also I set my nic to the correct speed(100 full duplex) and do not use Auto Negotiate on my server.

[Toddly]

Open DCT has solved a number of problems for me vs. SageDCT yet I am having small pauses/halts regularly when viewing live tv or a recording. They occur roughly every 8-10 minutes. Anyone have a possible solution? I am not sure where to start. Running version 4.48.

Your help is appreciated.

[jgsouthard]

Originally Posted by Toddly

Open DCT has solved a number of problems for me vs. SageDCT yet I am having small pauses/halts regularly when viewing live tv or a recording. They occur roughly every 8-10 minutes. Anyone have a possible solution? I am not sure where to start. Running version 4.48.

Your help is appreciated.

EnterNoEscape may be able to look at your logs and see what is going on, but based on some of the experiences I've had I can think of a few things it MIGHT be OTHER than OpenDCT:

• Network issues (e.g. packet loss).
• Weak incoming TV cable signal (e.g. too many splitters in the line, bad cable, etc.).
• Computer resources (e.g. CPU utilization, disk performance).

If you are using HDHomeRun or HDHomeRun Prime tuners, I'd start by running the network packet loss test I referred to a few posts up. Or run some other network quality test, if you are using other tuners.

If your network is clean, then you can start looking into other possible issues. But if you are dropping a lot of packets due to a bad NIC/switch/cable, you could pull your hair out for a long time trying to fix other issues (voice of experience).

[Toddly]

Originally Posted by jgsouthard

EnterNoEscape may be able to look at your logs and see what is going on, but based on some of the experiences I've had I can think of a few things it MIGHT be OTHER than OpenDCT:

• Network issues (e.g. packet loss).
• Weak incoming TV cable signal (e.g. too many splitters in the line, bad cable, etc.).
• Computer resources (e.g. CPU utilization, disk performance).

If you are using HDHomeRun or HDHomeRun Prime tuners, I'd start by running the network packet loss test I referred to a few posts up. Or run some other network quality test, if you are using other tuners.

If your network is clean, then you can start looking into other possible issues. But if you are dropping a lot of packets due to a bad NIC/switch/cable, you could pull your hair out for a long time trying to fix other issues (voice of experience).

Thanks for the help. I will look into those issues but HDhomerun QuickTV runs smoothly. Is the packet loss test from Silicon Dust? I use the HDHomerun Prime.Gonna check the built in NIC first.

[EnterNoEscape]

Originally Posted by Toddly

Thanks for the help. I will look into those issues but HDhomerun QuickTV runs smoothly. Is the packet loss test from Silicon Dust? I use the HDHomerun Prime.Gonna check the built in NIC first.

If you can post your log, that will probably give me a hint about what's going on.

[jgsouthard]

Originally Posted by Toddly

Thanks for the help. I will look into those issues but HDhomerun QuickTV runs smoothly. Is the packet loss test from Silicon Dust? I use the HDHomerun Prime.Gonna check the built in NIC first.

If QuickTV works well, then it probably isn't a signal strength issue. But it could still be a network issue in the path between the HDHRP's and SageTV, for example the NIC in SageTV or a switch between the tuners and SageTV.

The packet loss test is part of the SiliconDust software provided with the HDHomeRun tuners as an option on the hdhomerun_config command. While it isn't a general purpose utility and can't tell you anything about network speed, it tests packet transfers directly to/from the tuners themselves, and I don't know any other easy way to do that. (Just be sure to run hdhomerun_config on the SageTV PC, and not from some other PC where you may have loaded the SiliconDust software.)

Your network hardware is probably fine, but in the couple of cases where I had issues (both of them marginal NIC's), I spent untold hours troubleshooting the wrong problems. So in cases like this where the whole setup depends so heavily on clean network traffic, I've learned the hard way to START the troubleshooting there.

By the way, I'd recommend heavily loading the HDHR tuners and the SageTV NIC before running the network packet loss test. Pick a period (several hours if possible) where you don't need to make recordings, load up the NIC with other network traffic, set SageTV to record on all except one of your available tuners, then start the packet test on the one remaining tuner and let it run for several hours.

To generate other network traffic on the NIC, you can copy a set of large files (e.g. your SageTV recordings) from the SageTV PC to another device on the network. Ideally you want traffic in both directions, so if possible copy large files both TO and FROM the SageTV PC at the same time.

I did that one my motherboard NIC and found problems, switched to a discrete Intel NIC and ran the tests again and confirmed the problems were gone; and that got rid of most of the ongoing halts, pixelation, and pauses I was getting.

[Toddly]

Originally Posted by jgsouthard

If QuickTV works well, then it probably isn't a signal strength issue. But it could still be a network issue in the path between the HDHRP's and SageTV, for example the NIC in SageTV or a switch between the tuners and SageTV.

The packet loss test is part of the SiliconDust software provided with the HDHomeRun tuners as an option on the hdhomerun_config command. While it isn't a general purpose utility and can't tell you anything about network speed, it tests packet transfers directly to/from the tuners themselves, and I don't know any other easy way to do that. (Just be sure to run hdhomerun_config on the SageTV PC, and not from some other PC where you may have loaded the SiliconDust software.)

Your network hardware is probably fine, but in the couple of cases where I had issues (both of them marginal NIC's), I spent untold hours troubleshooting the wrong problems. So in cases like this where the whole setup depends so heavily on clean network traffic, I've learned the hard way to START the troubleshooting there.

By the way, I'd recommend heavily loading the HDHR tuners and the SageTV NIC before running the network packet loss test. Pick a period (several hours if possible) where you don't need to make recordings, load up the NIC with other network traffic, set SageTV to record on all except one of your available tuners, then start the packet test on the one remaining tuner and let it run for several hours.

To generate other network traffic on the NIC, you can copy a set of large files (e.g. your SageTV recordings) from the SageTV PC to another device on the network. Ideally you want traffic in both directions, so if possible copy large files both TO and FROM the SageTV PC at the same time.

I did that one my motherboard NIC and found problems, switched to a discrete Intel NIC and ran the tests again and confirmed the problems were gone; and that got rid of most of the ongoing halts, pixelation, and pauses I was getting.

Sounds good. I will test this tomorrow. Not much recording during the day. Its the Warriors tonight.

Thank You

[Daweeze]

Originally Posted by Toddly

........Its the Warriors tonight.

Yes it is.....go Dubs!!!

-Travis

[troll5501]

Still running 0.4.48 and tonight the entire JVM crashed with a segmentation fault in avformat...this is the first I ever saw this with OpenDCT. Below is the wrapper.log output at the time of the crash and I am attaching the JVM error file with the stack trace. EnterNoEscape, let me know if you have any thoughts or if you need any additional information or logs.

INFO   | jvm 1    | 2016/05/03 20:00:07.369 | 20:00:07.296 [FFmpegTransSageTVConsumerImpl-65493:DCT-HDHomeRun Prime Tuner 13191941-0] INFO  FFmpegStreamDetection - Before avformat_find_stream_info() pos=167132 bytes_read=167132 seek_count=0. probesize: 165440 analyzeduration: 0.
INFO   | jvm 1    | 2016/05/03 20:00:07.570 | 20:00:07.556 [FFmpegTransSageTVConsumerImpl-65493:DCT-HDHomeRun Prime Tuner 13191941-0] ERROR mpeg2video - Repeated 37 times: [0x7fcd08caa2c0] Invalid frame dimensions -1834274656x0..
INFO   | jvm 1    | 2016/05/03 20:00:07.570 | 20:00:07.556 [FFmpegTransSageTVConsumerImpl-65493:DCT-HDHomeRun Prime Tuner 13191941-0] ERROR mpeg2video - [0x7fcd08533320] Invalid frame dimensions -1834274656x0.
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | 20:00:07.685 [FFmpegTransSageTVConsumerImpl-65493:DCT-HDHomeRun Prime Tuner 13191941-0] INFO  FFmpegStreamDetection - After avformat_find_stream_info() pos=0 bytes_read=1169883 seek_count=2. probesize: 165440 analyzeduration: 0.
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # A fatal error has been detected by the Java Runtime Environment:
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | #  SIGSEGV (0xb) at pc=0x00007fcd30dd3527, pid=17236, tid=140519625467648
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # JRE version: Java(TM) SE Runtime Environment (8.0_72-b15) (build 1.8.0_72-b15)
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.72-b15 mixed mode linux-amd64 compressed oops)
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # Problematic frame:
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # C
INFO   | jvm 1    | 2016/05/03 20:00:07.870 |   [libjniavformat.so+0x31527]  Java_org_bytedeco_javacpp_avformat_00024AVStream_codec__+0x47
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | # An error report file with more information is saved as:
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | # /var/log/opendct/hs_err_pid17236.log
ERROR  | wrapper  | 2016/05/03 20:00:07.922 | JVM exited unexpectedly.
STATUS | wrapper  | 2016/05/03 20:00:07.922 | JVM exited in response to signal UNKNOWN (6).
INFO   | jvm 1    | 2016/05/03 20:00:07.922 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.922 | # If you would like to submit a bug report, please visit:
INFO   | jvm 1    | 2016/05/03 20:00:07.922 | #   http://bugreport.java.com/bugreport/crash.jsp
INFO   | jvm 1    | 2016/05/03 20:00:07.922 | #

[EnterNoEscape]

Originally Posted by troll5501

Still running 0.4.48 and tonight the entire JVM crashed with a segmentation fault in avformat...this is the first I ever saw this with OpenDCT. Below is the wrapper.log output at the time of the crash and I am attaching the JVM error file with the stack trace. EnterNoEscape, let me know if you have any thoughts or if you need any additional information or logs.

INFO   | jvm 1    | 2016/05/03 20:00:07.369 | 20:00:07.296 [FFmpegTransSageTVConsumerImpl-65493:DCT-HDHomeRun Prime Tuner 13191941-0] INFO  FFmpegStreamDetection - Before avformat_find_stream_info() pos=167132 bytes_read=167132 seek_count=0. probesize: 165440 analyzeduration: 0.
INFO   | jvm 1    | 2016/05/03 20:00:07.570 | 20:00:07.556 [FFmpegTransSageTVConsumerImpl-65493:DCT-HDHomeRun Prime Tuner 13191941-0] ERROR mpeg2video - Repeated 37 times: [0x7fcd08caa2c0] Invalid frame dimensions -1834274656x0..
INFO   | jvm 1    | 2016/05/03 20:00:07.570 | 20:00:07.556 [FFmpegTransSageTVConsumerImpl-65493:DCT-HDHomeRun Prime Tuner 13191941-0] ERROR mpeg2video - [0x7fcd08533320] Invalid frame dimensions -1834274656x0.
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | 20:00:07.685 [FFmpegTransSageTVConsumerImpl-65493:DCT-HDHomeRun Prime Tuner 13191941-0] INFO  FFmpegStreamDetection - After avformat_find_stream_info() pos=0 bytes_read=1169883 seek_count=2. probesize: 165440 analyzeduration: 0.
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # A fatal error has been detected by the Java Runtime Environment:
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | #  SIGSEGV (0xb) at pc=0x00007fcd30dd3527, pid=17236, tid=140519625467648
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # JRE version: Java(TM) SE Runtime Environment (8.0_72-b15) (build 1.8.0_72-b15)
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.72-b15 mixed mode linux-amd64 compressed oops)
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # Problematic frame:
INFO   | jvm 1    | 2016/05/03 20:00:07.770 | # C
INFO   | jvm 1    | 2016/05/03 20:00:07.870 |   [libjniavformat.so+0x31527]  Java_org_bytedeco_javacpp_avformat_00024AVStream_codec__+0x47
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | # An error report file with more information is saved as:
INFO   | jvm 1    | 2016/05/03 20:00:07.870 | # /var/log/opendct/hs_err_pid17236.log
ERROR  | wrapper  | 2016/05/03 20:00:07.922 | JVM exited unexpectedly.
STATUS | wrapper  | 2016/05/03 20:00:07.922 | JVM exited in response to signal UNKNOWN (6).
INFO   | jvm 1    | 2016/05/03 20:00:07.922 | #
INFO   | jvm 1    | 2016/05/03 20:00:07.922 | # If you would like to submit a bug report, please visit:
INFO   | jvm 1    | 2016/05/03 20:00:07.922 | #   http://bugreport.java.com/bugreport/crash.jsp
INFO   | jvm 1    | 2016/05/03 20:00:07.922 | #

The code behind this is actually very simple and does almost everything possible to prevent this from happening. Every single step is checked to make sure it points to an actual object. It's almost safe to say this is a bug in FFmpeg, but there is one more thing that can be checked and I'll make sure it makes it into 0.5 (probably not 0.4), because I think this particular bug is very rare.