[Sugar-devel] Killing activities when memory gets short
tomeu at sugarlabs.org
Sun Aug 8 09:33:19 EDT 2010
On Sun, Aug 8, 2010 at 15:15, Martin Langhoff <martin.langhoff at gmail.com> wrote:
> On Sun, Aug 8, 2010 at 4:01 AM, Tomeu Vizoso <tomeu at sugarlabs.org> wrote:
>> I tihnk I have been sloppy with my words, so let me clarify two things:
>> - killing processes should be done only to avoid OOM (because
>> currently the kernel kills the wrong thing most of the time).
> Can't we just _close it nicely_?
When you are about to get into OOM? Don't think so because it's very
probable that the kernel will block or kill something randomly before
the activity or the user react. But as I said, before we reach this
point we should have given the activities and/or the user the option
to avoid this situation.
> I have extremely rarely seen a Sugar app not closing. Sugar shell can
> decide it's a good idea to close an activity because too many are open
> and system is under memory pressure.
> Sugar apps auto-save, so closing nicely should work very nicely...
> martin.langhoff at gmail.com
> martin at laptop.org -- School Server Architect
> - ask interesting questions
> - don't get distracted with shiny stuff - working code first
> - http://wiki.laptop.org/go/User:Martinlanghoff
More information about the Sugar-devel