Memory Leak when calling batch_update containing a np.nan
sam-watttime opened this issue · 0 comments
sam-watttime commented
When calling batch_update with a np.array containing an nan, I would expect it to either ignore the nan, or raise an error. It seems to raise an error if batch_update contains a NoneType (which np.nan is not).
Instead, the process just gobbles up as much memory as it can find.