Thread Subject:

Clear all doesn't clear the entire memory

Hello,

Sometimes, and when i run some files (especially the MEX files), my memory gets full.

Clear all command doenst erase the entire memory therefore i am forced to close and open matlab again.

Any advice on how can i clear my memory without having to close and open matlab ?

Thank you

Bluebird wrote:
> Hello,
>
> Sometimes, and when i run some files (especially the MEX files), my
> memory gets full.

> Clear all command doenst erase the entire memory therefore i am forced
> to close and open matlab again.
...

Sounds as though likely the MEX files aren't releasing all their memory
if it occurs mostly with them.

Which OS? Not sure Windoes is very good about actually releasing
process memory even if requested--newer versions may be better in that
regard???

--

Thank you. I use windows XP, yet i have 7 in another computer and still have the same issue.

The problem is, I know close to nothing when it comes to MEX file, so i don't know all the stuff about releasing memory :(...

Bluebird wrote:
> Thank you. I use windows XP, yet i have 7 in another computer and still
> have the same issue.
> The problem is, I know close to nothing when it comes to MEX file, so i
> don't know all the stuff about releasing memory :(...

Well, assuming these are files you wrote, time to start debugging them.
  Excepting for variables created explicitly to be passed back to the
Matlab workspace, any and all memory allocated within the Mex function
has to be released there as well to avoid memory leaks. That shouldn't
be too hard to follow.

OTOH, if they're from somewhere else then you're stuck unless you have
the source.

--

"Bluebird " <wlouis@ryerson.ca> wrote in message <i6tntl$7oe$1@fred.mathworks.com>...
> Thank you. I use windows XP, yet i have 7 in another computer and still have the same issue.
>
> The problem is, I know close to nothing when it comes to MEX file, so i don't know all the stuff about releasing memory :(...

doc clear

% did you try:

clear functions

% Clears all the currently compiled M-functions and MEX-functions from memory.
% Using clear function removes debugging breakpoints in the function M-file and reinitializes persistent variables, since the breakpoints for a function and persistent variables are cleared whenever the M-file is changed or cleared.

"someone" <someone@somewhere.net> wrote in message <i6tohs$iei$1@fred.mathworks.com>...
> "Bluebird " <wlouis@ryerson.ca> wrote in message <i6tntl$7oe$1@fred.mathworks.com>...
> > Thank you. I use windows XP, yet i have 7 in another computer and still have the same issue.
> >
> > The problem is, I know close to nothing when it comes to MEX file, so i don't know all the stuff about releasing memory :(...
>
> doc clear
>
> % did you try:
>
> clear functions
>
> % Clears all the currently compiled M-functions and MEX-functions from memory.
> % Using clear function removes debugging breakpoints in the function M-file and reinitializes persistent variables, since the breakpoints for a function and persistent variables are cleared whenever the M-file is changed or cleared.

I will give it a shot.. I thought clear all includes all the subsequent things (i.e. classes, functions, java etc).

"Bluebird " <wlouis@ryerson.ca> wrote in message <i6tpcd$dl3$1@fred.mathworks.com>...
> "someone" <someone@somewhere.net> wrote in message <i6tohs$iei$1@fred.mathworks.com>...
> > "Bluebird " <wlouis@ryerson.ca> wrote in message <i6tntl$7oe$1@fred.mathworks.com>...
> > > Thank you. I use windows XP, yet i have 7 in another computer and still have the same issue.
> > >
> > > The problem is, I know close to nothing when it comes to MEX file, so i don't know all the stuff about releasing memory :(...
> >
> > doc clear
> >
> > % did you try:
> >
> > clear functions
> >
> > % Clears all the currently compiled M-functions and MEX-functions from memory.
> > % Using clear function removes debugging breakpoints in the function M-file and reinitializes persistent variables, since the breakpoints for a function and persistent variables are cleared whenever the M-file is changed or cleared.
>
> I will give it a shot.. I thought clear all includes all the subsequent things (i.e. classes, functions, java etc).

Clear functions doenst help !

Bluebird wrote:
...

> Clear functions doenst help !

Of course not if your functions have memory leak(s)...

--

"Bluebird " <wlouis@ryerson.ca> wrote in message <i6tpls$3m1$1@fred.mathworks.com>...
> "Bluebird " <wlouis@ryerson.ca> wrote in message <i6tpcd$dl3$1@fred.mathworks.com>...
> > "someone" <someone@somewhere.net> wrote in message <i6tohs$iei$1@fred.mathworks.com>...
> > > "Bluebird " <wlouis@ryerson.ca> wrote in message <i6tntl$7oe$1@fred.mathworks.com>...
> > > > Thank you. I use windows XP, yet i have 7 in another computer and still have the same issue.
> > > >
> > > > The problem is, I know close to nothing when it comes to MEX file, so i don't know all the stuff about releasing memory :(...
> > >
> > > doc clear
> > >
> > > % did you try:
> > >
> > > clear functions
> > >
> > > % Clears all the currently compiled M-functions and MEX-functions from memory.
> > > % Using clear function removes debugging breakpoints in the function M-file and reinitializes persistent variables, since the breakpoints for a function and persistent variables are cleared whenever the M-file is changed or cleared.
> >
> > I will give it a shot.. I thought clear all includes all the subsequent things (i.e. classes, functions, java etc).
>
> Clear functions doenst help !


The person above is right. it's something to do with your mex file. if it's written in c++ then you probably don't have a destructor for one of your constructors. so as said before, either fix the mex file, or close then restart matlab every time you have a problem

Many thanks for your help people. I will see if I can fix the mex file otherwise i will live with the restart thing :).

Regards