MATLAB: Do I receive a segmentation violation when I update the model diagram for a model with an unconnected input port in a subsystem in Simulink 6.0 (R14)

6.0automaticallydiagramhandleinputmodelportr14ratesegmentationsimulinksubsystemtransitionunconnectedupdateviolation

I have a Simulink model with a triggered subsystem that has an input port which is not connected inside the subsystem. This input port is fed by block whose sample time is different from trigger signal sample time. Also, I have checked the 'Automatically handle rate transition' option in the configuration parameters.
I get the following segmentation violation when I update the model diagram for this model:
 Stack Trace:                                                               
   [0]                                                                      
 libmwsimulink.so:SetCompTsInfoForPortBasedBlkAfterTsProp(slBlockDiagram_tag 
 const*, slBlock_tag*)(0x08de42e0, 0x095d86e0, 1, 1) + 524 bytes            
   [1] libmwsimulink.so:.L398(0x095d86e0, 0, 0xbfff7288, 1) + 677 bytes    
   [2] libmwsimulink.so:insertRateTransBlock(slBlock_tag*, int, int,        
 bool)(0x094a1620, 0, 1, 1) + 130 bytes                                     
   [3] libmwsimulink.so:slInsertRateTransBlocks(slBlockDiagram_tag*,        
 SleCompilerDataMem*)(0x08de42e0, 0x09646cb8, 11, 0x42298ad0                 
 "TmpRateTransition_Feeding_Subsys..") + 331 bytes                          
   [4] libmwsimulink.so:sleCompileBlockDiagram(slBlockDiagram_tag*, bool,   
 SimType, mxArray_tag*)(0x08de42e0, 0, 1, 0) + 4245 bytes                   
   [5] libmwsimulink.so:.L141(0x095bda30, 0xbfff7464, 0, 0x4008e534) + 266  
 bytes                                                                      
   [6] libmwsimulink.so:sleInitModel(slModel_tag*, sleInitModelContext,     
 bool)(0x095bda30, 1, 0, 0) + 60 bytes                                      
   [7] libmwsimulink.so:sleUpdateDiagram(slGraph_tag*)(0x0944baf0,          
 0x08de42e0, 0xbfff7508, 0x518fd2ee) + 306 bytes                 
 [snip]

Best Answer

This bug has been fixed for Release 14 SP1 (R14SP1). For previous releases, please read below for any possible workarounds:
This has been verified as a bug in Simulink 6.0 (R14) in the way that it handles the 'Automatically handle rate transition' option along with an unconnected input port.
Currently, to work around this issue, try removing the unconnected input port.
Related Question