MATLAB: Does Simulink crash when editing signal name

simulink

Simulink crashes with the following stack trace when editing the signal name
Abnormal termination:
Access violation
Register State (from fault):
RAX = 00000000c1ede080 RBX = 0000000000000000
RCX = 0000000000000000 RDX = 00000000ffffffff
RSP = 00000000043f9a60 RBP = 0000000000000000
RSI = 000000023892d780 RDI = 000000023892d780
R8 = 000000023892d780 R9 = 0000000120b62338
R10 = 0000000000000080 R11 = 00000000043f9a80
R12 = 0000000129790a20 R13 = 0000000471aa3210
R14 = 0000000000000000 R15 = 0000000000000000
RIP = 0000000124b3b424 EFL = 00010206
CS = 0033 FS = 0053 GS = 002b
Stack Trace (from fault):
[ 0] 0x0000000124b3b424 bin\win64\SimulinkBlock.dll+00242724 slPort::getGrIsBlockOwner+00000004
[ 1] 0x00000001292691ff bin\win64\sl_compile.dll+00561663 SlSignalLabelProp::PortSupportsSigProp+00000015
[ 2] 0x000000012045a769 bin\win64\libmwsimulink.dll+17409897 pmEvaluateEngineBlockParams+00040265
[ 3] 0x0000000129254ac9 bin\win64\sl_compile.dll+00477897 SlBusLabelPropChangeCollector::addToGraphs+00003225
[ 4] 0x0000000129254f34 bin\win64\sl_compile.dll+00479028 SlUndoableBusLabelPropChangeCollector::applyChanges+00000996
[ 5] 0x0000000129254d3b bin\win64\sl_compile.dll+00478523 SlUndoableBusLabelPropChangeCollector::applyChanges+00000491
[ 6] 0x000000020ab47a4b bin\win64\sl_editor.dll+04160075 Simulink::GlyphDisplayRegistry::registerDisplayInfo+00151243
[ 7] 0x000000020ab48889 bin\win64\sl_editor.dll+04163721 Simulink::GlyphDisplayRegistry::registerDisplayInfo+00154889
[ 8] 0x0000000209bb867b bin\win64\glue2.dll+01083003 GLUE2::Command::handleDo+00000667
[ 9] 0x00000000fbfedc21 bin\win64\glee_util.dll+00515105 GLEE::Command::doIt+00000385
[ 10] 0x00000000fbff2228 bin\win64\glee_util.dll+00533032 GLEE::UndoRedoCommandTarget::processCommand+00000216
[ 11] 0x0000000209cbe5b9 bin\win64\glue2.dll+02155961 GLUE2::Editor::processCommand+00000297
[ 12] 0x000000020ab49850 bin\win64\sl_editor.dll+04167760 Simulink::GlyphDisplayRegistry::registerDisplayInfo+00158928
[ 13] 0x000000020ab4ae64 bin\win64\sl_editor.dll+04173412 Simulink::GlyphDisplayRegistry::registerDisplayInfo+00164580
[ 14] 0x0000000123651501 bin\win64\mg.dll+01578241 MG2::TextNode::getTextChangedEmitter+00013457
[ 15] 0x00000000fc001da1 bin\win64\glee_util.dll+00597409 GLIM::ConnectedPacket::deliver+00000049
[ 16] 0x00000000fc001218 bin\win64\glee_util.dll+00594456 GLIM::EmitterBase::sendPacket+00000440
[ 17] 0x0000000123653d03 bin\win64\mg.dll+01588483 MG2::TextNode::getTextChangedEmitter+00023699
[ 18] 0x00000001236449c5 bin\win64\mg.dll+01526213 MG2::Node::unsetCursor+00043413
[ 19] 0x0000000123646da0 bin\win64\mg.dll+01535392 MG2::Node::unsetCursor+00052592
[ 20] 0x000000012364a5c3 bin\win64\mg.dll+01549763 MG2::Node::unsetCursor+00066963
[ 21] 0x0000000123694600 bin\win64\mg.dll+01852928 MG2::TextNode::isToolBarVisible+00003504
[ 22] 0x00000001236c756b bin\win64\mg.dll+02061675 MG2::RolloverFactory::~RolloverFactory+00024715
[ 23] 0x0000000123717532 bin\win64\mg.dll+02389298 MG2::GLCanvas::exitTextEditMode+00000418
[ 24] 0x00000001237b7448 bin\win64\mg.dll+03044424 MG2::Rollover::clearManager+00041736
[ 25] 0x00000001237b82ff bin\win64\mg.dll+03048191 MG2::Rollover::clearManager+00045503
[ 26] 0x00000001237bb6d9 bin\win64\mg.dll+03061465 MG2::Rollover::clearManager+00058777
[ 27] 0x00000000fc001da1 bin\win64\glee_util.dll+00597409 GLIM::ConnectedPacket::deliver+00000049
[ 28] 0x00000000fc0068f6 bin\win64\glee_util.dll+00616694 GLIM::Thread::processCurrentQueue+00000150
[ 29] 0x00000001223e68d0 bin\win64\glee.dll+00288976 GLDebugOutputLogging::output+00001024
[ 30] 0x00000001223c9b2a bin\win64\glee.dll+00170794 checkMultiMVM+00033818
[ 31] 0x00000001223dbf7c bin\win64\glee.dll+00245628 GLIMMessageBlocker::~GLIMMessageBlocker+00007004
[ 32] 0x00000001223c32bf bin\win64\glee.dll+00144063 checkMultiMVM+00007087
[ 33] 0x00000001223c9ae6 bin\win64\glee.dll+00170726 checkMultiMVM+00033750
[ 34] 0x00000001223c4393 bin\win64\glee.dll+00148371 checkMultiMVM+00011395
[ 35] 0x00000001223df626 bin\win64\glee.dll+00259622 GLIMMessageBlocker::~GLIMMessageBlocker+00020998
[ 36] 0x00000000fd0080f7 bin\win64\iqm.dll+00491767 iqm::PackagedTaskPlugin::PackagedTaskPlugin+00000759
[ 37] 0x00000000fd0088bf bin\win64\iqm.dll+00493759 iqm::PackagedTaskPlugin::execute+00000879
[ 38] 0x00000000fd00817d bin\win64\iqm.dll+00491901 iqm::PackagedTaskPlugin::PackagedTaskPlugin+00000893
[ 39] 0x00000000fd008708 bin\win64\iqm.dll+00493320 iqm::PackagedTaskPlugin::execute+00000440
[ 40] 0x00000000152c5651 bin\win64\mcr.dll+00349777 OnlineLicenseManagementLauncher::~OnlineLicenseManagementLauncher+00010049
[ 41] 0x00000000fcfdbd3a bin\win64\iqm.dll+00310586 iqm::Iqm::setupIqmFcnPtrs+00079802
[ 42] 0x00000000fcfdbc06 bin\win64\iqm.dll+00310278 iqm::Iqm::setupIqmFcnPtrs+00079494
[ 43] 0x00000000fcfbeb65 bin\win64\iqm.dll+00191333 iqm::Iqm::deliver+00001397
[ 44] 0x00000000fb5fd3c3 bin\win64\libmwbridge.dll+00054211 ioReadLine+00000547
[ 45] 0x00000000fb5fd262 bin\win64\libmwbridge.dll+00053858 ioReadLine+00000194
[ 46] 0x00000000fb60d7de bin\win64\libmwbridge.dll+00120798 mnDebugPrompt+00001966
[ 47] 0x00000000fb60d170 bin\win64\libmwbridge.dll+00119152 mnDebugPrompt+00000320
[ 48] 0x00000000fb60db63 bin\win64\libmwbridge.dll+00121699 mnParser+00000547
[ 49] 0x00000000152abdb1 bin\win64\mcr.dll+00245169 mcr::runtime::setInterpreterThreadSingletonToCurrent+00029793
[ 50] 0x00000000152aace5 bin\win64\mcr.dll+00240869 mcr::runtime::setInterpreterThreadSingletonToCurrent+00025493
[ 51] 0x00000000152aad53 bin\win64\mcr.dll+00240979 mcr::runtime::setInterpreterThreadSingletonToCurrent+00025603
[ 52] 0x00000000152ab6e1 bin\win64\mcr.dll+00243425 mcr::runtime::setInterpreterThreadSingletonToCurrent+00028049
[ 53] 0x00000000fd02cc77 bin\win64\iqm.dll+00642167 iqm::UserEvalPlugin::pre+00028951
[ 54] 0x00000000fd039cfc bin\win64\iqm.dll+00695548 iqm::UserEvalPlugin::pre+00082332
[ 55] 0x00000000fd02737f bin\win64\iqm.dll+00619391 iqm::UserEvalPlugin::pre+00006175
[ 56] 0x00000000fd02cc16 bin\win64\iqm.dll+00642070 iqm::UserEvalPlugin::pre+00028854
[ 57] 0x00000000fd027863 bin\win64\iqm.dll+00620643 iqm::UserEvalPlugin::pre+00007427
[ 58] 0x00000000fd03c8b6 bin\win64\iqm.dll+00706742 iqm::UserEvalPlugin::pre+00093526
[ 59] 0x00000000fd0080f7 bin\win64\iqm.dll+00491767 iqm::PackagedTaskPlugin::PackagedTaskPlugin+00000759
[ 60] 0x00000000fd0088bf bin\win64\iqm.dll+00493759 iqm::PackagedTaskPlugin::execute+00000879
[ 61] 0x00000000fd00817d bin\win64\iqm.dll+00491901 iqm::PackagedTaskPlugin::PackagedTaskPlugin+00000893
[ 62] 0x00000000fd008708 bin\win64\iqm.dll+00493320 iqm::PackagedTaskPlugin::execute+00000440
[ 63] 0x00000000fcfdbd3a bin\win64\iqm.dll+00310586 iqm::Iqm::setupIqmFcnPtrs+00079802
[ 64] 0x00000000fcfdbc06 bin\win64\iqm.dll+00310278 iqm::Iqm::setupIqmFcnPtrs+00079494
[ 65] 0x00000000fcfbf5be bin\win64\iqm.dll+00193982 iqm::Iqm::deliver+00004046
[ 66] 0x00000000fcfc0545 bin\win64\iqm.dll+00197957 iqm::Iqm::deliver+00008021
[ 67] 0x00000001001237c1 bin\win64\libmwservices.dll+01259457 services::system_events::PpeDispatchHook::dispatchOne+00021505
[ 68] 0x0000000100128663 bin\win64\libmwservices.dll+01279587 sysq::addProcessPendingEventsUnitTestHook+00002211
[ 69] 0x0000000100128850 bin\win64\libmwservices.dll+01280080 sysq::addProcessPendingEventsUnitTestHook+00002704
[ 70] 0x0000000100129c26 bin\win64\libmwservices.dll+01285158 sysq::getCondition+00003462
[ 71] 0x000000010012ac66 bin\win64\libmwservices.dll+01289318 svWS_ProcessPendingEvents+00000230
[ 72] 0x00000000152ac244 bin\win64\mcr.dll+00246340 mcr::runtime::setInterpreterThreadSingletonToCurrent+00030964
[ 73] 0x00000000152ac964 bin\win64\mcr.dll+00248164 mcr::runtime::setInterpreterThreadSingletonToCurrent+00032788
[ 74] 0x00000000152a2762 bin\win64\mcr.dll+00206690 mcr_process_events+00008818
[ 75] 0x00000000151e23c5 bin\win64\MVMLocal.dll+00271301 mvm_server::inproc::LocalFactory::terminate+00088005
[ 76] 0x00000000fa957669 bin\win64\mvm.dll+01209961 mvm::detail::initLocalMvmHack+00000569
[ 77] 0x00000000fa957e2b bin\win64\mvm.dll+01211947 mvm::detail::SessionImpl::privateSession+00000555
[ 78] 0x00000000fa958051 bin\win64\mvm.dll+01212497 mvm::detail::SessionImpl::privateSession+00001105
[ 79] 0x0000000140007833 bin\win64\MATLAB.exe+00030771
[ 80] 0x000000014000863f bin\win64\MATLAB.exe+00034367
[ 81] 0x00007ffd0fa58364 <file:///C:/Windows/System32/KERNEL32.DLL+00033636 C:\Windows\System32\KERNEL32.DLL+00033636> BaseThreadInitThunk+00000020
[ 82] 0x00007ffd11ef70d1 <file:///C:/Windows/SYSTEM32/ntdll.dll+00422097 C:\Windows\SYSTEM32\ntdll.dll+00422097> RtlUserThreadStart+00000033

Best Answer

This is a bug found in R2017a and R2017b. This bug was fixed as of R2018a.
Simulink can crash when editing the name of a signal, when both of these conditions exist:
1) The name is edited by double-clicking on the signal line in the Simulink Editor.
2) The name is propagated through a Configurable Subsystem.
If you have a current subscription to MathWorks Software Maintenance Service (SMS), you can download product updates.
If upgrading is not an option, you can use one of these approaches:
1) Change the name of the signal using the Signal Properties dialog instead of double-clicking on the signal line.
2) Upgrade the Configurable Subsystem blocks in your model to Variant Subsystem blocks.
See the following bug report for more details: