> The problem for us is that we currently don't construct any of these > RootedObject instances, which means that the SpiderMonkey internal GC
Really? My layer calls, for example, JS_ConstructObjectWithArguments() to make a new object, I would suppose you replace that with some kind of js new call, which implicitly or explicitly creates a new object in c++, which calls the constructor you described, and I would figure that's good enough to keep it around, until we remove it, which use to be some kind of js_free, now some kind of js_destroy, and then the gc can clean up the loose ends, and I'm sorry in advance if I'm oversimplifying it, because I haven't looked at any of your code or how it works; I just didn't expect a problem here. Allocate becomes new construct, and all should be well. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
