I'm on the V8 team, and I defer to Ben on this question :-) I've never tried embedding two different versions of V8 into the same process, and I don't think we'd consider that scenario supported, but it may well work. You can probably find out with a fairly small example (i.e. without sinking lots of time into it) whether it works.
With regards to memory, I implemented first/second chance weak handle > callbacks and tested it with low memory limits for semi/old space sizes and > it appears to deal with memory restrictions well. What Ben pointed out was virtual memory reservations, which is not the same as restricted space sizes. As he said, on 64-bit platforms it shouldn't be a problem. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
