We're looking for a person or people to help audit MDN to find places we could speed up. Is this you or someone you know? Check out the RFP: https://mzl.la/2IHcMiE


Obsolete since JSAPI 13
This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.

Unregister a custom string memory manager.


JS_RemoveExternalStringFinalizer(JSStringFinalizeOp finalizer);
Name Type Description
finalizer JSStringFinalizeOp The finalizer to remove.


Remove finalizer from the global GC finalizers table, returning its type code if found, -1 if not found.

As with JS_AddExternalStringFinalizer, there is a threading restriction if you compile the engine JS_THREADSAFE: this function may be called for a given finalizer pointer on only one thread; different threads may call to remove distinct finalizers safely.

You must ensure that all strings with finalizer's type have been collected before calling this function. Otherwise, string data will be leaked by the GC, for want of a finalizer to call.

See Also

Document Tags and Contributors

 Contributors to this page: teoli, arai, fscholz, tschneidereit, Jorend
 Last updated by: teoli,