Remove SafeFreePool from MemoryAllocationLib as this API's name is misleading. Its implementation only check if a pointer is NULL. If a garbage pointer is passed in, the gBS->FreePool will still ASSERT in debug build and return error code.

It is recommended that module writer should keep track how a pointer is allocated and free it after use.

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@6307 6f19259b-4bc3-4df7-8a09-765794883524

EdkCompatibilityPkg/Compatibility/FrameworkHiiToUefiHiiThunk/Strings.c

@@ -378,7 +378,9 @@ Returns:
   }
 
 Done:
-  SafeFreePool (Iso639AsciiLanguage);
+	if (Iso639AsciiLanguage != NULL) {
+    FreePool (Iso639AsciiLanguage);
+  }
   
   return Status;
 }