> I think you can already set these parameters through the API. That seems > like > the right way forward, rather than using build-time macros. > > http://codereview.chromium.org/2737002/show >
Hi Eric, I agree that using the API method to override the default Heap configuration is the best way forward. We had attempted to use the method but the configuration was failing with the error indicating that the heap had already been configured. This was with the Chrome browser code. Most likely, we are missing the correct binding entry points between V8 and webkit causing V8 to get initialized down some other path. Is there a easy way to identify all of the points within the source at which V8 has been bound to webkit on Chrome? Thanks, Dineel -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
