[Octave-bug-tracker] [bug #59597] bogus result returned by mexCallMATLAB

[Rik]

Follow-up Comment #5, bug #59597 (project octave):

Can you add this code to the end of the mex C file?


  int i;
  for (i = 0; i < 3; i++)
    mxDestroyArray (x[i]);


This frees the memory from the heap that was allocated internally by
mexCallMATLAB.  I don't think it is necessary because it should be the case
that when the mex file finishes execution Octave reclaims any memory
associated with it.  But, if Octave is not doing that properly then it could
cause issues.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59597>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/