The reason I ask is that I have an application that (among other things) calls a MATLAB .NET component whenever data is written into a specific file. The component reads the file and creates an image out of the data contained within. This works fine.
However when I am using the underlying application to additionally process a “significant” amount of data and display the processed data in table, the call to MATLAB throws an out of memory exception, but only when I am processing this large amount of data.
Is this not an indication that the MATLAB process called will rely on the available memory of the application? I guess I just don’t understand how the MATLAB memory works when being called from a .NET standpoint.
(I should also note that I call clear all before every call to the MATLAB function in an attempt to “start from scratch”, but it fails regardless)
COMcomponents built byMatlab Builder NEare in-processCOMservers. This means that they areDLLs which are loaded into your application memory space. This means that theMCR, which is a kind ofMatlab-Virtual-Machineis in your memory space.I believe that
.NETcomponents should behave exactly the same.