<div class="gmail_quote">On Mon, Mar 9, 2009 at 9:56 AM, Gary C Martin <span dir="ltr"><<a href="mailto:gary@garycmartin.com">gary@garycmartin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 9 Mar 2009, at 13:28, Tomeu Vizoso wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Feb 24, 2009 at 03:38, Wade Brainerd <<a href="mailto:wadetb@gmail.com" target="_blank">wadetb@gmail.com</a>> wrote:</blockquote></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What about watching system resources and refusing to start a new activity<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
when there isn't enough RAM available to launch it?<br>
It should be pretty straightforward to add a required_memory field to<br>
<a href="http://activity.info" target="_blank">activity.info</a> - it would be a simple, approximate high water mark memory<br>
usage for a given activity. The default could be determined by analyzing<br>
the basic activities - maybe 20mb would be good?<br>
</blockquote>
<br>
Are we sure this is a good experience for our users? I remember that<br>
in the old MacOS times, I found a bit tiring to have to go to the<br>
applications' info panel to lower the memory limits so the app could<br>
launch.<br>
</blockquote>
<br></div></div>
Yea, that was rather a frequent support call back in my early Adobe days :-) Set it too low and they can't open some document, to high and they can't run the other couple of applications they needed open at the same time to work.</blockquote>
<div><br></div><div>Even a warning alert would be better than nothing. </div><div><br></div><div>Your computer is too low on memory to start this activity. </div><div>Are you sure you want to start Browse?</div><div><br>
</div><div>It happens to me at least once every couple of days on build 767...first the UI freezes, then the trackpad stops responding, and if I'm lucky I can manage to Ctrl-Alt-F1 and kill Browse before having to just hard power off. And that's just with GMail (in Browse), a Terminal, and Typing Turtle (which is admittedly a memory hog due to all the cached key graphics).</div>
<div><br></div><div>Also, I think we should really consider implementing that kernel OOM watch feature. Activities save their state when you tab away from them, so in a lot of cases it's safe to just kill background activities.</div>
<div><br></div><div>Best,</div><div>Wade</div><div><br></div></div>