Thread Subject: out of memory when using a breakpoint

Hello,

while running the code the normal way usually makes no problem I get
an

??? Error using ==> zeros
Out of memory. Type HELP MEMORY for your options.

when I set a breakpoint within an function.

Rebooting the computer or restarting MATLAB doesn't help.

Many thanks, Ingo

exabwu <exabwu@googlemail.com> wrote in message <3951b89a-71a5-4e62-bf6d-d21b13b763c8@r37g2000prr.googlegroups.com>...
> Hello,
>
> while running the code the normal way usually makes no problem I get
> an
>
> ??? Error using ==> zeros
> Out of memory. Type HELP MEMORY for your options.
>
> when I set a breakpoint within an function.
>
> Rebooting the computer or restarting MATLAB doesn't help.
>
> Many thanks, Ingo

Hello,

I believe you have written something like this:

zeros(10000)

when you wanted to make up a column or row vector. The way to fix this is to say

zeros(10000,1);

Hope this helps.

On 19 Jan., 15:40, "Sadik " <sadik.h...@gmail.com> wrote:
> exabwu<exa...@googlemail.com> wrote in message <3951b89a-71a5-4e62-bf6d-d21b13b76...@r37g2000prr.googlegroups.com>...
> > Hello,
>
> > while running the code the normal way usually makes no problem I get
> > an
>
> > ??? Error using ==> zeros
> > Out of memory. Type HELP MEMORY for your options.
>
> > when I set a breakpoint within an function.
>
> > Rebooting the computer or restarting MATLAB doesn't help.
>
> > Many thanks, Ingo
>
> Hello,
>
> I believe you have written something like this:
>
> zeros(10000)
>
> when you wanted to make up a column or row vector. The way to fix this is to say
>
> zeros(10000,1);
>
> Hope this helps.


Thanks for you reply!

Actually we used MSaturation = zeros(1,2);

It only happens once in a while ?!

exabwu wrote:
 
> while running the code the normal way usually makes no problem I get
> an

> ??? Error using ==> zeros
> Out of memory. Type HELP MEMORY for your options.
 
> when I set a breakpoint within an function.

I -speculate- that you might have a variable that is not used, or perhaps even
a computation sequence which produces a result that is not used. -Possibly-
when you run normally, the Just In Time (JIT) compiler does not bother creating
the variable. When you set a breakpoint, though, because you might want to
examine any of the variables, the JIT cannot omit that variable -- and having
that variable might happen to cause you to run out of memory.

There are additional possibilities if you are running a function by putting
your cursor in the function in the editor and pressing F5: if you are
doing that, then there are situations where you could run into that kind
of problem if you have a name conflict between one of your variables and
one of the matlab routines: in such a case, when you ran "normally", the
JIT will (in some situations) call the Matlab routine instead of using
the variable of the same name {if the variable was "poofed into existance"
by load() or assignin() or eval() or similar mechanism, instead of being
the target of a visible assignment statement.}
--
.signature note: I am now avoiding replying to unclear or ambiguous postings.
Please review questions before posting them. Be specific. Use examples of what you mean,
of what you don't mean. Specify boundary conditions, and data classes and value
relationships -- what if we scrambled your data or used -Inf, NaN, or complex(rand,rand)?