There's a patch attached to LUCENENET-106 for 2.3.1 that has never been
committed to the real SVN repository. Does 2.3.1 still need the fix or has
the memory leak been addressed in another fashion and the bug simply hasn't
been updated to reflect that?

 

Thanks,

 

Jason

Reply via email to