MATLAB: Does MATLAB crash when trying to open certain data files from the Current Directory browser

crashcurrentdirectoryMATLAB

Why does MATLAB crash and give the following error when trying to open certain data files from the Current Directory browser?
----------
Assertion detected at Fri May 24 14:15:35 2002
----------
Assertion failed: (hdr->in_use != 0), at line 870 of file "./mwmem.c".
Attempt to free previously freed memory
Configuration:
MATLAB Version: 6.0.0.88 (R12)
Operating System: Microsoft Windows NT
Window System:Version 4.0 (Build 1381: Service Pack 6)
Processor ID: x86 Family 6 Model 8 Stepping 1, GenuineIntel
Virtual Machine:Java 1.1.8 from Sun Microsystems Inc.
Stack Trace:
[0] matlab.exe:_mnSignalHandler(0xffffffff, 0, 0, 1) + 452 bytes
[1] matlab.exe:_ThrowAssertion(0x028dc2e8, 1, 0x65737341, 0x6f697472) + 167 bytes
[2] matlab.exe:_MATLABAssertFcn(0x015df108 ": (hdr->in_use != 0),", 0x015deaa4 "./mwmem.c", 870, 0x015df120 "Attempt to free previously freed..") + 131 bytes
[3] libut.dll:_ut_assertstr(0x015df108 ": (hdr->in_use != 0),", 0x015deaa4 "./mwmem.c", 870, 0x015df120 "Attempt to free previously freed..") + 25 bytes
[4] libut.dll:_mw_free(0x028dc2f0 "_fiFullFlushFcn", 0, 0x02995728, 0x014b26f8) + 239 bytes
[5] libut.dll:_utFree(0x028dc2f0 "_fiFullFlushFcn", 0x014b2704, 0x0041db83, 0x028dc2f0 "_fiFullFlushFcn") + 25 bytes
[6] libmx.dll:_mxFree(0x028dc2f0 "_fiFullFlushFcn", 0x014b2718, 0x0041b4ac, 0x02995728) + 32 bytes
[7] matlab.exe:_matTerminateMATFile4(0x02995728, 0, 0x014b3428, 0x014b3618) + 19 bytes
[8] matlab.exe:_matClose(0x02995728, 0x014b3671, 0x24901935, 0x24901918 "C:\TEMP\matlab_crash_dump.312") + 12 bytes
[9] matlab.exe:_fiSaveFcnWithLHS(939, 0x014b3654 "f:\MatlabStuff\boilerroom.dat", 0, 0x014b3b54) + 5785 bytes
[10] matlab.exe:_nmFullLoadFcn(1, 0x014b3c58, 2, 0x014b3e28) + 724 bytes
[11] m_interpreter.dll:_inExecuteInternalFcn(53, 2, 1, 0) + 1144 bytes
[12] m_interpreter.dll:_inInterPcode(1, 72, 0x02a31328, 0x02a31e20 "FileType") + 2206 bytes
[snip]

Best Answer

This problem has been reported to our development staff for further investigation.
There are currently no known workarounds.