MathWorks Technical Support Advisory – R2007a Windows DVDs
The MathWorks has identified a manufacturing process error that caused one batch of R2007a Windows version DVDs containing a version of Simulink with several known bugs to be shipped to customers. New product orders placed between March 1 and April 2, 2007 were affected.
To verify if you have the incorrect Windows version DVD, look at the date of the following file:
$MATLABROOT\bin\win32\libmwsimulink.dll or
$MATLABROOT\bin\win64\libmwsimulink.dllwhere $MATLABROOT is the MATLAB root directory on your machine, as returned
by typing matlabroot
at the MATLAB Command Prompt.
If the date of the file is 2/3/2007, you will need to replace your DVD. However, if the date of the file is 2/8/2007, you do not need to replace your DVD.
R2007a software users who installed from the incorrect Windows version DVD should take the following actions:
I. Download Updated Software
The bugs on the incorrect DVDs caused memory leaks, problems with creating UIs, and crashes in the following products:
- Real-Time Workshop®
- Simulink®
- Simulink HDL Coder
- Simulink Fixed Point
Note: This issue did not impact the R2007a updated product release shipped to maintenance subscribers.
II. Replace the Windows Version DVD
Replacement DVDs have been shipped to customers. Please discard the Windows version DVD shipped with the original new product order.
III. Review Related Information
Following is a list of critical bug fixes in R2007a that were missing from the Windows version DVD shipped:
a) Memory
leak issue using Bus Selector connected to root Inport or Outport in
referenced model
Description: Memory leaks might occur in Simulink when the model has the following characteristics:
- The model contains a Model block
- The referenced model contains a Bus signal
- The Bus signal is connected in one or both of the following ways:
- A Bus Selector selects a bus signal element from the root Inport
- A Bus Selector selects a bus signal element and outputs it to the root Outport
b) Memory
leak issue when a large number of blocks are connected outside of a conditionally
executed subsystem that allows execution context propagation across the subsystem
boundary
Description: Simulink memory leaks might occur when model has the following characteristics:
- The model contains a conditionally executed subsystem that allows execution context propagation across the subsystem boundary.
- There are more than 128 blocks connected outside of the conditionally executed subsystem.
c) Checking whether model is "shadowing" other
files takes up too much of model load time.
Description: When loading a model, Simulink checks to see whether other files
on the MATLAB path, or variables in the MATLAB workspace have the same name
as the model.
If so, Simulink issues the following warning:
The model name 'mymodel' is shadowing another name in the MATLAB workspace
or path... You should change the name of the model to avoid problems.
This check can take up to 4% of the total time taken to load the model and provides limited benefit to the user.
d) Some Simulink HDL Coder GUI options are not functional
Description: Options in the top-level HDL Coder pane of the Simulink Configuration
Parameters dialog box (and the Simulink Model Explorer) are not functional.
e) Fixed-Point Tool might fail to open for models saved in prior Simulink
versions
Description: The Fixed-Point Tool might fail to open if all the following
conditions apply:
- You created your model in a prior version of Simulink.
- In the prior Simulink version, you saved your model while the Fixed-Point Tool was open.
- You load that model in Simulink 6.6 (R2007a Prerelease).
- In Simulink 6.6 (R2007a Prerelease), you simulate that model before opening the Fixed-Point Tool.
In this rare situation, subsequent attempts to open the Fixed-Point Tool might fail.
You can work around this issue using any of the following methods:
- Open the Fixed-Point Tool prior to simulating your model.
- If you already simulated your model before opening the Fixed-Point Tool,
enter the following command at the MATLAB prompt:
clear fxptdlgand then try opening the Fixed-Point Tool.
f) External mode: memory leak when running model connected to target crashes
MATLAB
Description: When running a Simulink model that is connected to a target using
external mode, a memory leak causes memory for MATLAB.exe to continually increase. Eventually,
memory is exhausted and MATLAB crashes.
Store