valgrind检测到paddle预测库内存泄漏

多线程运行后发现内存泄漏，程序可以肯定的是已经delete掉LAC对象了，是我的用法有问题么？
at 0x4C2A1E3: operator new(unsigned long) (vg_replace_malloc.c:334)
==2286== by 0x124DE9BD: paddle::framework::details::OpInfoFiller::o
perator()(char const*, paddle::framework::OpInfo*) const (in /mnt/sdd/wzx/dynamicwfst_hisf/lib/libpaddle_fluid.so)
==2286== by 0x124DF2D8: paddle::framework::OperatorRegistrar, paddle::framework::EmptyGradOpMaker >::OperatorRegistrar(char const*) (in /mnt/sdd/
wzx/dynamicwfst_hisf/lib/libpaddle_fluid.so)

Start with the Valgrind trace for libpaddle_fluid.so, especially OpInfoFiller and OperatorRegistrar around GenerateProposalLabelsOp. Reproduce the multithreaded run after deleting the LAC object and determine whether the reported allocation remains reachable or leaked; the issue is resolved only when the ownership or usage cause is identified.

Written by the indexing model from the issue text.