Handbrake Nightly-20190225 not working
I would like an indication of whether or not this is likely to be a bug suitable for reporting on Github.
On my PC, the latest nightly build from https://handbrake.fr/nightly.php cannot be launched, while the latest stable build (version 1.2.2 from a few days ago) starts up just fine.
The exception details I'm getting are as follows:
Code: Select all
An Unknown Error has occurred.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.EntryPointNotFoundException: Unable to find an entry point named 'hb_get_build' in DLL 'hb'.
at HandBrake.Interop.Interop.HbLib.HBFunctions.hb_get_build(IntPtr hbHandle)
at HandBrake.Interop.Utilities.VersionHelper.IsNightly() in C:\HandBrake\hbworkspace\workspace\WindowsGui64\win\CS\HandBrake.Interop\Utilities\VersionHelper.cs:line 47
at HandBrakeWPF.Services.UserSettingService..ctor() in C:\HandBrake\hbworkspace\workspace\WindowsGui64\win\CS\HandBrakeWPF\Services\UserSettingService.cs:line 40
--- End of inner exception stack trace ---
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Caliburn.Micro.SimpleContainer.ActivateInstance(Type type, Object[] args)
at Caliburn.Micro.SimpleContainer.<>c__DisplayClass7_0.<RegisterSingleton>b__0(SimpleContainer container)
at HandBrakeWPF.Startup.AppBootstrapper.GetInstance(Type service, String key) in C:\HandBrake\hbworkspace\workspace\WindowsGui64\win\CS\HandBrakeWPF\Startup\AppBootstrapper.cs:line 129
at Caliburn.Micro.IoC.Get[T](String key)
at HandBrakeWPF.App.OnStartup(StartupEventArgs e) in C:\HandBrake\hbworkspace\workspace\WindowsGui64\win\CS\HandBrakeWPF\App.xaml.cs:line 100
at System.Windows.Application.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
aka https://i.imgur.com/pkKByXR.png (topic render appears to be broken..)
"An Unknown Error has occured.
If the problem persists, please try restarting HandBrake.
Error Details: >> (refer to code spoiler above)
Steps to reproduce the problem (If Applicable):
1) Download the nightly that was built today, from https://handbrake.fr/nightly.php, version HandBrake-20190225-ee3a464_x86_64-Win_GUI.exe
2) Attempt to start the application
3) Perhaps get the crash that I am getting, being unable to proceed
HandBrake version (e.g., 1.0.0):
HandBrake-20190225-ee3a464_x86_64-Win_GUI
Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update):
Windows 10 17763.316 (latest build as of writing). Hardware specs:
AMD FX-8350 Octa core CPU
ATI Radeon R9 290 4GB GPU with Radeon driver version 19.2.2
16GB RAM
HandBrake Activity Log ***required*** (see How-to get an activity log)
activity_log61596.txt contains:
Code: Select all
Cannot load nvEncodeAPI64.dll
Things like this make me think I might be better off in the support forum rather than the Github issue tracker. I would like triage first.
Is this exception a known problem?
Once again, the stable build runs fine for me. Also, the amount of files that are in folders C:\Program Files\HandBrake Nightly versus C:\Program Files\HandBrake match (except for GongSolutions.Wpf.DragDrop.pdb being present in release version but not in the nightly install folder). So I have a hard time believing it's missing a dependency somewhere.
Note: There are no WER (Windows Error Reporting) reports and crash dumping by using a WER registry entry seems not to be possible, probably because the exception handler is manually implemented and is what is shown in my image. If I can do more to get better details, please let me know.