<HTML>
<BLOCKQUOTE TYPE=CITE>
<BR><FONT FACE="sans-serif"><FONT SIZE=-1>Weird cause Im using windows
with some 750 MB's of ram (*1.2 swap files)</FONT></FONT>
<BR><FONT FACE="sans-serif"><FONT SIZE=-1>MC usually doesn't go beyond
30MB's of ram usage (go figure for what!)</FONT></FONT>
<P><FONT FACE="sans-serif"><FONT SIZE=-1>To me part of the problem seems
that the allocation of the image space in the</FONT></FONT>
<BR><FONT FACE="sans-serif"><FONT SIZE=-1>stack is not "solid" - it is
not compactable it seems for one, and once an image</FONT></FONT>
<BR><FONT FACE="sans-serif"><FONT SIZE=-1>is decompressed, that's it, you're
stuck with that size...</FONT></FONT>
<BR> </BLOCKQUOTE>
<P>Well, I'm not sure if this is gonna help, but I have
<BR>the feeling it's a memory problem.
<P>I always develop my stacks on Mac (OS 9 so far)
<BR>and when I do multiple successive "set filename of
<BR>img 1" (for an img control used as background
<BR>graphic), it seems that previous content of that img
<BR>control isn't purged from memory, and that successive
<BR>replacements finally crash the app.
<BR>Perhaps is it related to the fact that the "always buffer"
<BR>prop of that img is set to true... I don't know...
<P>I also noticed that "set filename of img 1 to empty"
<BR>before setting filename to another file leads to less
<BR>crashes.
<P>I only experienced these problems in edit mode.
<BR>In standalones everything's works perfect...
<P>JB</HTML>