MATLAB: HDF5.dll version conflict between MCR 9.1 and the application

hdf5 .net

MyApp is a C# .NET v4.5.2 WPF app. MyAssembly is a Matlab .NET assembly I created containing MyClass. MyAssembly requires MCR v9.1. MyApp performs various tasks; when one requires Matlab and it tries to instantiate MyClass then a popup window displays:

% The procedure entry point H5Rdereference could not be located in dynamic link library C:\Program Files\MATLAB\MATLAB Runtime\v91\bin\win64\libmat.dll.

MyApp contains a version of hdf5.dll (obtained from Nuget package HDF.PInvoke v1.10.1), and I discovered that MCR 9.1 also contains a (different) version of hdf5.dll in C:\Program Files\MATLAB\MATLAB Runtime\v91\bin\win64. When I replaced MyApp's version of that dll with MCR 9.1's version, MyApp is able to instantiate MyClass, but then MyApp is no longer able to perform its HDF5 tasks; calls to H5.open() throw:

% Unable to load DLL 'hdf5.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)'

MyClass doesn't require HDF5, so why is the MCR loading its copy of that DLL? How do I get around this conflict?

Best Answer

There is no getting around it. HDF5.dll is native. All users of HDF5.dll in a given process must use the same version.

Related Solutions

MATLAB: Is the AUTOSAR model crashing with std::terminate() in autosar::BlockMapping or autosar::ModelMapping

MATLAB might crash with the following stack trace when working with an Simulink AUTOSAR model.

If you experience this crash and can reproduce the issue, please comment below or contact < MathWorks Technical Support>:

[  0] 0x000000001084b2c3                              bin\win64\libmwfl.dll+00045763 foundation::core::diag::thread_context::unspecified_bool+00000051
[  1] 0x0000000010849288                              bin\win64\libmwfl.dll+00037512 foundation::core::diag::stacktrace_base::capture+00000024
[  2] 0x000000001084e750                              bin\win64\libmwfl.dll+00059216 foundation::core::diag::symbols::getSymbolAddress+00012656
[  3] 0x000000001085299f                              bin\win64\libmwfl.dll+00076191 foundation::core::diag::is_terminate_message_enabled+00000607
[  4] 0x00000000174f4604                                  bin\win64\mcr.dll+01132036 mcr::shutdown::startWatchdog+00037076
[  5] 0x00000000174f3c77                                  bin\win64\mcr.dll+01129591 mcr::shutdown::startWatchdog+00034631
[  6] 0x00000000174ef4a0                                  bin\win64\mcr.dll+01111200 mcr::shutdown::startWatchdog+00016240
[  7] 0x00000000174f5b16                                  bin\win64\mcr.dll+01137430 mnSetSegvServiceUrl+00000214
[  8] 0x00007ffd90ab4b10 C:\Program Files\MATLAB\R2019a\bin\win64\VCRUNTIME140.dll+00019216 purecall+00000048
[  9] 0x00000002e03ad881                           bin\win64\sl_autosar.dll+00645249 autosar::CompositionModelMapping::getRoot+00081601
[ 10] 0x00000000f81a5cbd                  bin\win64\libmwsl_services_mi.dll+00089277 sl::mi::PropInfo::getValue+00000029
[ 11] 0x000000013c638802                          bin\win64\sl_loadsave.dll+01935362 slsWriteObject+00000578
[ 12] 0x000000002855003e                        bin\win64\pgo\mcos_impl.dll+00458814
[ 13] 0x000000002854b589                        bin\win64\pgo\mcos_impl.dll+00439689
[ 14] 0x000000013c63840c                          bin\win64\sl_loadsave.dll+01934348 slsWriteCOSObject+00003612
[ 15] 0x000000013c637333                          bin\win64\sl_loadsave.dll+01930035 slsWriteCOSArray+00000243
[ 16] 0x00000002931c1815                 bin\win64\sl_graphical_classes.dll+06297621 slWritePrmDesc+00000261
[ 17] 0x000000015936a1db                    bin\win64\sl_prm_descriptor.dll+00106971 SLCOSPrmDesc::bdWrite_Impl+00000187
[ 18] 0x00000002931c17c0                 bin\win64\sl_graphical_classes.dll+06297536 slWritePrmDesc+00000176
[ 19] 0x00000002931c1672                 bin\win64\sl_graphical_classes.dll+06297202 PrmDescBDWriteBlock+00000146
[ 20] 0x0000000293207323                 bin\win64\sl_graphical_classes.dll+06583075 BlockParamGroup::saveOneParameter+00000083
[ 21] 0x00000002931b5035                 bin\win64\sl_graphical_classes.dll+06246453 slBasicParamGroup::doSave+00000149
[ 22] 0x0000000293207297                 bin\win64\sl_graphical_classes.dll+06582935 BlockParamGroup::save+00000135
[ 23] 0x0000000292c4a03a                 bin\win64\sl_graphical_classes.dll+00565306 slParamGroup::saveAll+00000042
[ 24] 0x00000002b981aef8                        bin\win64\libmwsimulink.dll+08957688 slSave::WriteBlockDiagram+00009720
[ 25] 0x00000002b981ac27                        bin\win64\libmwsimulink.dll+08956967 slSave::WriteBlockDiagram+00008999
[ 26] 0x00000002b981ec2e                        bin\win64\libmwsimulink.dll+08973358 slSave::WriteBlockDiagram+00025390
[ 27] 0x00000002b981adde                        bin\win64\libmwsimulink.dll+08957406 slSave::WriteBlockDiagram+00009438
[ 28] 0x00000002b981ec2e                        bin\win64\libmwsimulink.dll+08973358 slSave::WriteBlockDiagram+00025390
[ 29] 0x00000002b981adde                        bin\win64\libmwsimulink.dll+08957406 slSave::WriteBlockDiagram+00009438
[ 30] 0x00000002b981ec2e                        bin\win64\libmwsimulink.dll+08973358 slSave::WriteBlockDiagram+00025390
[ 31] 0x00000002b981a259                        bin\win64\libmwsimulink.dll+08954457 slSave::WriteBlockDiagram+00006489
[ 32] 0x00000002b98190f5                        bin\win64\libmwsimulink.dll+08950005 slSave::WriteBlockDiagram+00002037
[ 33] 0x00000002b9818938                        bin\win64\libmwsimulink.dll+08948024 slSave::WriteBlockDiagram+00000056
[ 34] 0x00000002b981fbd6                        bin\win64\libmwsimulink.dll+08977366 slSave::WriteBlockDiagram+00029398
[ 35] 0x0000000292dc1606                 bin\win64\sl_graphical_classes.dll+02102790 SLXSinglePartHandler::doSave+00000246
[ 36] 0x0000000292dc1411                 bin\win64\sl_graphical_classes.dll+02102289 slBlockDiagramMatData::writeMDL+00015553
[ 37] 0x0000000292dc263e                 bin\win64\sl_graphical_classes.dll+02106942 SLXPartHandler::getSaveOptions+00001150
[ 38] 0x00000000285370d0                        bin\win64\pgo\mcos_impl.dll+00356560
[ 39] 0x0000000028536872                        bin\win64\pgo\mcos_impl.dll+00354418
[ 40] 0x000000002853596b                        bin\win64\pgo\mcos_impl.dll+00350571
[ 41] 0x0000000028569636                        bin\win64\pgo\mcos_impl.dll+00562742
[ 42] 0x0000000028599e0c                        bin\win64\pgo\mcos_impl.dll+00761356
[ 43] 0x000000002879d35d                        bin\win64\pgo\mcos_impl.dll+02872157 mwboost::serialization::singleton_module::unlock+01547437
[ 44] 0x00000000287a6f45                        bin\win64\pgo\mcos_impl.dll+02912069 mwboost::serialization::singleton_module::unlock+01587349
[ 45] 0x0000000014bd37f5                                 bin\win64\mcos.dll+00145397 omDirectCallMethod+00000069
[ 46] 0x000000001b80966a                 bin\win64\pgo\libmwlxeindexing.dll+00366186 MathWorks::lxe::MatrixModuleImplementation::SetHeterogeneousArray+00014714
[ 47] 0x000000001b88bdea                 bin\win64\pgo\libmwlxeindexing.dll+00900586 MathWorks::lxe::assign_paren_shared_xvalue_ptr_uninitialized_to_struct+00006850
[ 48] 0x000000001b7bfc7f                 bin\win64\pgo\libmwlxeindexing.dll+00064639 MathWorks::lxe::at_rbrace_nargout+00002559
[ 49] 0x000000001b7bfc7f                 bin\win64\pgo\libmwlxeindexing.dll+00064639 MathWorks::lxe::at_rbrace_nargout+00002559
[ 50] 0x000000001b7f99ac                 bin\win64\pgo\libmwlxeindexing.dll+00301484 mwboost::serialization::singleton_module::unlock+00026324

MATLAB: Can the Assembly not be found when deserializing a .NET object in MATLAB 7.10 (R2010a)

Please note that the behavior described above is not a limitation of MATLAB. It is in fact expected behavior of the .NET framework.

By default when deserializing an object, the .NET Framework will only look for the required Assembly in the "EXE directory"; it will not even look for already loaded Assemblies.

To make the deserialization work, you will thus need to either:

1. Place myAssembly1.dll in the $MATLABROOT\bin\[win32|win64] directory, or

2. Implement your own ResolveEventHandler for the AppDomain.CurrentDomain.AssemblyResolve event in myAssembly2. So for example in the constructor of myClass2 add:

AppDomain.CurrentDomain.AssemblyResolve += new ResolveEventHandler(CurrentDomain_AssemblyResolve);

To register your own ResolveEventHandler called CurrentDomain_AssemblyResolve. This CurrentDomain_AssemblyResolve could look like:

System.Reflection.Assembly CurrentDomain_AssemblyResolve(object sender, ResolveEventArgs args)
{
      System.Reflection.Assembly ayResult = null;
      string sShortAssemblyName = args.Name.Split(',')[0];
      System.Reflection.Assembly[] ayAssemblies = AppDomain.CurrentDomain.GetAssemblies();
      foreach (System.Reflection.Assembly ayAssembly in ayAssemblies)
      {
          if (sShortAssemblyName == ayAssembly.FullName.Split(',')[0])
          {
              ayResult = ayAssembly;
              break;
          }
      }
      return ayResult;
}

This particular ResolveEventHandler will allow you to use already loaded Assemblies when deserializing objects.

Best Answer

Related Solutions

MATLAB: Is the AUTOSAR model crashing with std::terminate() in autosar::BlockMapping or autosar::ModelMapping

MATLAB: Can the Assembly not be found when deserializing a .NET object in MATLAB 7.10 (R2010a)

Related Question