Release 12 Readme

MATLAB 6.0 Major Bug Fixes

MATLAB 5.3.1 Major Bug Fixes

Invisible figures cause focus changes to be slow (UNIX only)

Creating invisible figure windows caused Matlab to thrash the X server during focus changes. This his been fixed.

Invalid movies caused a segmentation violation

Previously, calling the movie command with a movie array in which one or more elements were unitialized caused a segmentation violation. This now causes an error.

getframe sometimes fails to capture uicontrols (UNIX only)

The getframe function now always captures uicontrols.

getframe fails with truecolor using less than 24 bits (UNIX only)

The getframe function now supports truecolor XWindows visuals using fewer than 24 bits.

Memory leaked when converting arrays from MATLAB to Java

Extensive use of the MATLAB/Java interface could result in exhaustion of system memory. This memory leak has been plugged.

Using CAT with cell or struct arrays may result in a crash

Certain usages of CAT with cell or struct arrays or empty arrays can result in a segmentation violation. This regression from MATLAB 5.2 has been corrected.

MATLAB may crash while reading a corrupt MAT-file

It is possible to encounter a segmentation violation when reading a corrupted MAT-file due to misplaced error check. This problem has been corrected.

Incorrect results when doing complex division in array initialization

A constant expression involving division by an imaginary number (e.g. 3/i) produced random results when used in forming an array.

Displaying structures with long field names can cause an assertion

Displaying structures with long field names can cause an "Attempt to free previously freed memory" assertion due to a flow-of-control error. This problem has been corrected.

Colon indexing with sparse cell arrys can cause an assertion

An expression of the form b{1} = sparse(eye(4)); b{1}(1,1) would cause an "Attempt to free previously freed memory" assertion. This problem has been fixed.

Error occurs when using GUIDE Control Panel

Opening the GUIDE Control Panel on Microsoft Windows with no open Figure windows can cause an error under certain circumstances. This problem has been corrected.

Old P-files may cause crash when displaying cell arrays or structures

Cell array or structure expressions that display their results (i.e., are not terminated with a semicolon) may result in a crash when run in MATLAB 5.3 if they were saved in a P-file with MATLAB 5.2 or earlier.

MATLAB may crash on HP systems with HP's Y2K patch (HP700 only)

A symbol name conflict between one of our third party libraries and one of HP's system libraries can cause MATLAB to crash when creating new files. This issue has been resolved via an updated library.

MATLAB may fail to start when running on IRIX 6.5 (SGI/SGI64 only)

IRIX 6.5 no longer ships with certain math libraries that MATLAB depends on. The missing libraries are now provided as part of the MATLAB distribution in $matlab/sys/os/sgi[64].