Closed richardhundt closed 1 year ago
@richardhundt Thank you for reporting this.
@richardhundt Again, thank you very much for the report and sorry for inconvenience. Hopefully, I fixed the leak (TBH, embarrassing bug). If you like, you may try the code directly from the master. Or wait until tomorrow (well, today's evening), I'll prepare a new release.
Better wait for the new release, a build failed.
OK, version 1.1.8 was released. @richardhundt please verify, if you can.
works perfectly now, thank you!
Hi, i'm sorry for opening such an old issue, but i'm currently experiencing the same issue. I'm using version 1.4.0 now and getting small steady memory leaks (after debugging with tracemalloc) on:
A = ahocorasick.Automaton() MyList = [...] for x in MyList: A.add_word(y, (y, z))
is there a chance this bug has returned
Thanks, Eden.
See https://github.com/WojciechMula/pyahocorasick/pull/166 where we have still a memory leak on unicode builds
Hello,
Can confirm memory leak issue exists in 1.4.4 and it might have something to do with pickling, tracemalloc output:
[ Top 10 ] /usr/lib/python3.8/multiprocessing/reduction.py:51: size=23.2 GiB, count=36957, average=659 KiB /usr/lib/python3.8/linecache.py:137: size=508 KiB, count=5133, average=101 B /usr/lib/python3.8/tracemalloc.py:65: size=60.1 KiB, count=962, average=64 B /usr/lib/python3.8/tracemalloc.py:185: size=42.2 KiB, count=900, average=48 B
@Azzonith I created https://github.com/WojciechMula/pyahocorasick/issues/183 to track your issue
@EdenAzulay You issue is tracked in https://github.com/WojciechMula/pyahocorasick/issues/135
Closing this one.
Version: 1.1.7 Python 3.6
Hi, I'm seeing a pretty drastic memory leak using
A.keys(...)
only. Is this expected?I'm doing the following:
That's it. My data sets are pretty large, but I obviously know when I'm in the second loop, and memory keeps growing without bound.