I had some questions about embedding + jemalloc. We made a change recently to link jemalloc directly into libxul instead of the app (where app == xulrunner, firefox-bin, TestGtkEmbed, etc.) See this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=418016 So I have a concern about this from an embedding standpoint. If we're using jemalloc's allocator instead of the normal system one, how will this affect apps that want to link against libxul or the library that we provide for embedding? Specifically: 1. If the jemalloc allocator gets loaded, does it change the allocator used by the app? If so, does that happen after the app has done some allocations and might cause mis-matched malloc/free pairs? 2. If the jemalloc allocator is loaded and is private to libxul, does this mean that embedding applications that are passed data that's allocated inside of libxul will have to use a xul-private free() function? Simple questions, but one we need to look at from an embedding standpoint. --Chris _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
