EE4 Pro在事件日志中与故障模块ntdll.dll消息崩溃 [英] EE4 Pro crashes with faulting module ntdll.dll message in the event log

问题描述

我有控制台应用程序使用EE4 Pro SDK使用多个线程编码多个视频文件。我有一组孤立的文件导致我的控制台应用程序崩溃。崩溃后事件日志中记录以下错误：
$


错误应用程序jobprocessor.exe，版本1.0.0.0，标记4c8e187e，错误模块ntdll.dll，版本5.2。 3790.4455，邮票49900d60，调试？ 0，故障地址0x0002bc52。





申请：JobProcessor.exe

框架版本：v4.0.30319

描述：由于未处理的异常，进程终止。

异常信息：异常代码c0000005，异常地址7C82BC52



我意识到这个问题很可能是由编解码器失败造成的。除了禁用故障编解码器之外，还可以采取哪些措施来提高编码器API的可靠性？尝试禁用硬件加速肯定会显着改善结果。永久禁用此选项的
副作用是什么？

 

 

解决方案

您正在遭遇本机崩溃，正如您所说，它与编解码器最相关，或者可能是错误的文件。 如果你能得到一个完整的原生callstack，我就能在这方面提供更多信息。

禁用硬件加速可能会降低某些编解码器/操作系统组合的预览性能。 在输出质量或编码性能方面它应该没有效果。

如果问题是编解码器/坏数据不好而您不想永久禁用编解码器，那么可以尝试一个包装过程。 基本上将JobPrecessor.exe调用到JobProcessorWorker.exe中进行编码。 然后，JobProcessor将监视
崩溃，如果它发现它可能会终止工作进程然后继续下一个文件。

Brian

 

I have console app that using EE4 Pro SDK to encode several video files using multiple threads. I have isolated group of files that cause my console app to crash. The following errors recorded in the event log after crash:

Faulting application jobprocessor.exe, version 1.0.0.0, stamp 4c8e187e, faulting module ntdll.dll, version 5.2.3790.4455, stamp 49900d60, debug? 0, fault address 0x0002bc52.


Application: JobProcessor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 7C82BC52

I realize that problem most likely caused by failed codec. Other than disabling faulting codec what can be done to improve reliability of the encoder API? Trying to disable hardware acceleration definitely improves outcomes significantly. What would be the side effect of permanently disabling this option?

 

 

解决方案

You are getting a native crash which as you say is most lickly related to codec or could be bad files.  If you could get a full native callstack i would be able to give more information on that front.

Disabling HW acceleration could reduce preview performance with some codec/OS combinations.  In terms of output quaility or encode performance it shouldn't have an effect.

If the problem is a bad codec/bad data and you don't want to disable the codec permently, you could try a wrapper process.  Basicly have your JobPrecessor.exe call into JobProcessorWorker.exe to do the encode.  JobProcessor would then watch for crashes which if it found it could kill the worker process and then continue on to the next file.

Brian

 

这篇关于EE4 Pro在事件日志中与故障模块ntdll.dll消息崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！