On Fri, May 21, 2010 at 9:26 PM, Erik Corry <[email protected]> wrote:
> In addition, when V8 exits it assumes that the process is about the exit. > Since the OS will clean up the memory, V8 won't bother to do a GC and won't > call your callbacks. Some people find this counterintuitive. Perl appears > to do a GC on exit. At least that was my conclusion on observing that a > fork followed by an exit takes a huge amount of time on a large perl > process. > Not to beat a dead horse, but it's not only counterintuitive, but semantically wrong for bound C/C++ types which require a destructor call for proper semantics. Examples include: - closing a db handle - flushing a stream handle before closing it - closing ncurses windows (not doing so hoses the screen state when the app exits). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
