summaryrefslogtreecommitdiffstats
path: root/fuzz/bplist-leaks/leak-acb3c00a83d7635638a476a4e70fc1f1caa1a5b1
diff options
context:
space:
mode:
authorGravatar Martin Szulecki2015-01-23 15:05:38 +0100
committerGravatar Martin Szulecki2015-01-23 15:05:38 +0100
commita11e8b1b9a7661a19a75ef4ffbff99e7adb1ec8d (patch)
tree4b0b92e2d7910b5ca4a01b5fb2075d746681c29d /fuzz/bplist-leaks/leak-acb3c00a83d7635638a476a4e70fc1f1caa1a5b1
parent8ed89366e45d594205cf6401ffe6852921ef2484 (diff)
downloadlibplist-a11e8b1b9a7661a19a75ef4ffbff99e7adb1ec8d.tar.gz
libplist-a11e8b1b9a7661a19a75ef4ffbff99e7adb1ec8d.tar.bz2
xplist: Plug memory leak by cleaning up libxml2's parser after use
This is actually considered bad practice. However, it appears this memory leak is otherwise not possible to fix due to a design flaw in how libxml2 handles the lifecycle of it's XML parser. We'll let the community test this in production now and decide. In our tests this change had no drawbacks except fixing the last known memory leak in libplist.
Diffstat (limited to 'fuzz/bplist-leaks/leak-acb3c00a83d7635638a476a4e70fc1f1caa1a5b1')
0 files changed, 0 insertions, 0 deletions