>> Did you try it, or is that just something you know without testing? >> I understand the principle, but I haven't seen the problem in practice on any platform.
It happens on all platforms. I posted an example which can be seen in the 'scrubbed html' at https://lists.webkit.org/pipermail/webkit-dev/2008-June/004073.html. >> If the problem is a real practical issue, do you have a suggested fix? >> Would you be willing to make a patch to show what it would look like? I provide a description of the primary typical solution that is used at: https://lists.webkit.org/pipermail/webkit-dev/2008-June/004071.html. Basically you don't directly invoke global operator new but instead use either a redirecting macro or use a custom version of new which takes an argument which identifies the heap you are targeting (possibly even single one for all of WebKit). I can understand that some developers who have spent a lot of time developing monolithic desktop or server software are used to using the built-in global operator new. The concept of controlling memory like I am proposing is the rule in commercial library development and not the exception. I humbly ask that the WebKit team consider migrating towards this type of development. It will make WebKit considerably stronger outside the desktop market, and yet is rather easy to apply. It's largely a matter of accepting an idea that is a little different from what some have done in the past. Thanks. _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev