Comment 12 for bug 2015962

Could you confirm that those loaded the new library version? Because I confirmed locally that the segfault and valgrind error were fixed with the new release, at least in the testcase described upstream (but could be that the issue referred to is different from the one reported/triggered by the testcase)