Check for custom free function in global destructor

Calling a custom deallocation function in the global destructor could
cause all kinds of unexpected problems. See for example

    sparklemotion/nokogiri#2059

Only clean up if memory is managed with malloc/free.

parser.c

@@ -14696,7 +14696,12 @@ xmlCleanupParser(void) {
 static void
 ATTRIBUTE_DESTRUCTOR
 xmlDestructor(void) {
-    xmlCleanupParser();
+    /*
+     * Calling custom deallocation functions in a destructor can cause
+     * problems, for example with Nokogiri.
+     */
+    if (xmlFree == free)
+        xmlCleanupParser();
 }
 #endif