MATLAB: Does MATLAB crash with jogl_desktop.dll in the crash dump

jogl_desktopjogl_desktopdllMATLAB

MATLAB is crashing in a number of different situations (opening Simulink model, using imagesc() function, etc) with jogl_desktop.dll in the stack trace section of the crash dump. How can I avoid this issue?

An example crash dump is as follows:

Stack Trace (captured):
[ 22] 0x000007feed53518a [unknown function] at C:\Windows\system32\OPENGL32.dll+151946 (no debugging symbols found)
[ 23] 0x000007feed535604 [unknown function] at C:\Windows\system32\OPENGL32.dll+153092 (no debugging symbols found)
[ 24] 0x0000000078da396e [unknown function] at \\mathworks\devel\bat\archive\R2016a\Prerelease\perfect\matlab\bin\win64\jogl_desktop.dll+342382 (no debugging symbols found)
[ 26] 0x00000000fffffffe [unknown function] at \\mathworks\devel\bat\archive\R2016a\Prerelease\perfect\matlab\bin\win64\libmwi18n.dll+1048574

Best Answer

Several users have reported this issue, and they were able to resolve it by updating their graphics card drivers.

If updating your graphics drivers does not help to prevent additional crashes, please contact Technical Support:

http://www.mathworks.com/support/contact_us/

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: MATLAB crashes when using graphics with older NVidia OpenGL drivers

MATLAB can abruptly exit when executing commands that use MATLAB graphics in a computer that utilizes older NVidia drivers.

To determine if you are experiencing this issue, the following three steps must be true:

1. The resulting crash log "matlab_crash_dump.XXXX" contains the "nvogl64.dll" keyword. Refer to the following article to find the crash log that was generated by MATLAB:

How do I locate the crash log files generated by MATLAB?

2. Your computer has an NVidia graphics card that uses a driver version older than the latest driver available. Refer to the following article to determine which driver version your computer uses:

How do I determine the version of my graphics card driver from my MATLAB crash log?

3. Refer to the following NVidia website to determine which is the latest available driver:

NVidia Driver Download

If your driver version is older, upgrading drivers may help resolve the crash. Please download and install the latest driver available for your graphics card.

Note that in some instances your operating system or computer manufacturer may say your drivers are up to date, however, the driver information is still older than the driver available from the Nvidia website.

Alternate workaround:

For some NVidia graphics drivers, you may be able to work around this behavior by changing the profile the driver utilizes. To do so follow these steps:

1. Open the NVidia control panel

2. Under 3D Settings, select the Manage 3D Settings panel

3. Under the Global Settings panel, click on the Global Presets drop-down list to choose "Dassault Systems - CATIA compatible" profile

On Windows machines, you can set this profile automatically if NVidia WMI is installed by running the following command at the Windows Command Prompt:

wmic /namespace:\\root\CIMV2\NV path ProfileManager call setCurrentProfile3D "Dassault Systemes CATIA - compatible"

Best Answer

Related Solutions

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

MATLAB: MATLAB crashes when using graphics with older NVidia OpenGL drivers

Related Question