MATLAB: Do I receive a segmentation violation when I attempt to load a workspace using MATLAB 7.0 (R14)

activexMATLABsegfaultsegv

When MATLAB is being run as a COM server and I attempt to load a workspace using File -> Load Workspace… in the newly created MATLAB command window, I receive a segmentation violation.
 ------------------------------------------------------------------------
        Segmentation violation detected at Fri Dec 03 09:14:55 2004
 ------------------------------------------------------------------------
 Configuration:
   MATLAB Version:   7.0.0.19920 (R14)
   Operating System: Microsoft Windows XP
   Window System:    Version 5.1 (Build 2600: Service Pack 1)
   Processor ID:     x86 Family 15 Model 2 Stepping 9, GenuineIntel
   Virtual Machine:  Java 1.4.2 with Sun Microsystems Inc. Java HotSpot(TM) Client VM
     (mixed mode)
   Default Charset:  ibm-5348_P100-1997
 Register State:
   EAX = 00000005  EBX = 00000001
   ECX = 00cdaf00  EDX = 79066f05
   ESI = 00000000  EDI = 00000005
   EBP = 00cda9dc  ESP = 00cda8bc
   EIP = 79032340  FLG = 00010202
 Stack Trace:
   [0] uiw.dll:char * __cdecl buildFilterStrings(char const * *,char const * *,int,char const * *,char const * *)(0, 1, 0, 0) + 448 bytes
   [1] uiw.dll:int __cdecl SelectFile(struct SelectFileParamInfo *)(0x00cdaf50, 0x018894f8, 0x64616f4c, 0x616d2e20) + 97 bytes
   [2] uiw.dll:void __cdecl uiwm_loadmat(void)(0, 0x018894f8, 1008, 0) + 107 bytes
   [3] uiw.dll:long __cdecl OnCmdCommand(struct HWND__ *,int,int,int)(853406, 273, 1008, 0) + 908 bytes
   [4] uiw.dll:public: virtual int __thiscall CCmdFrame::OnCommand(unsigned int,long)(1008, 0, 0x018894f8, 0x018894f8) + 30 bytes
   [5] MFC71.DLL:0x7c175cf2(273, 1008, 0, 0x00cdb080)
   [6] MFC71.DLL:0x7c16e0b0(273, 1008, 0, 0x00cdb1a4)
   [7] MFC71.DLL:0x7c16e14f(0, 853406, 273, 1008)
   [8] MFC71.DLL:0x7c16e1b8(853406, 273, 1008, 0)
 ...

Best Answer

This bug has been fixed in Release 14 Service Pack 3 (R14SP3). For previous product releases, read below for any possible workarounds:
This problem has been fixed in MATLAB 7.0.1 (R14SP1). If you are using a previous version, read the following:
We have verified that there is a bug in MATLAB 7.0 (R14) that affects the way the load dialog operates when MATLAB is run as a COM server. To work around this issue, you can load from the command prompt using the LOAD command or execute the command through the COM interface.
Related Question