On Tue, Sep 4, 2012 at 8:54 AM, Carsten Haitzler <ras...@rasterman.com> wrote: > On Mon, 3 Sep 2012 18:45:58 -0300 Gustavo Sverzut Barbieri > <barbi...@profusion.mobi> said: >> Really bad >> >> -1000 > > agreed. if u abort() or segv() it makes little difference. for small data > structs (linked list nodes for example) its VERY hard to recover sensibly from > such an out-of-memory situation. but for large allocs its perfectly possible. > a > blanket "abort on fail" is bad. really bad. ESPECIALLY for a wm. we try and > recover in a lot of cases. but there is a lot of allocation going on. > > also the same crash happens when you run out of stack space - no way to > recover > or detect actually...
I also dislike the abort scenario, much better to have a proper safe exit scenario. -- Cedric BAIL ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
