Re:This is the exploit equivalent of that guy who played the...
by tedunangst on Monday July 06, 2009 @08:24PM
(#690704)
In the case of a browser plugin, I'd be quite annoyed if an out of memory condition in the plugin caused my whole browser to quit. I'd experience something beyond annoyance if printing caused my word processor to quit without saving. The never fail malloc wrapper makes sense for some programs, but not for others where better, context sensitive recovery is possible.
[ Parent
| on HN ]
Re:This is the exploit equivalent of that guy who played the...
by dbenamy on Monday July 06, 2009 @08:49PM
(#690723)
In the context of a browser plugin, "quit" could just mean to stop executing and throw up an error message. It doesn't necessarily mean to end the whole process (browser).
Re:This is the exploit equivalent of that guy who played the...
by tedunangst on Monday July 06, 2009 @10:02PM
(#690777)
Throwing up an error message is likely to require allocating some of the memory you just ran out of. There's very little you can reasonably expect to do when you run out of memory. The caller needs to carefully back out, but this isn't something a wrapper can do by itself.
Re:This is the exploit equivalent of that guy who played the...
by mfukar on Tuesday July 07, 2009 @02:39AM
(#691045)
Strings are still statically allocated (courtesy of C compilers everywhere), right?
and I guess if you have to make one function call to throw an error message, there's some room left in the stack..
and then there's the whole virtual memory thing..
but I could be reasonably wrong. :-)