You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I also get this ~sometimes on shutdown for a different program -- but I haven't been able to make a minimal reproduction of that:
ObjectCache(0x7f12443ae1e0)::~ObjectCache(): WARNING! LEAK! object 0x5634c6dbf0e0 still has count 1 (id .../venv/share/tessdata/eng.traineddatalstm-punc-dawg)ObjectCache(0x7f12443ae1e0)::~ObjectCache(): WARNING! LEAK! object 0x5634c6e35e40 still has count 1 (id .../venv/share/tessdata/eng.traineddatalstm-word-dawg)ObjectCache(0x7f12443ae1e0)::~ObjectCache(): WARNING! LEAK! object 0x5634c6e579d0 still has count 1 (id .../venv/share/tessdata/eng.traineddatalstm-number-dawg)
I don't think either of these outputs should be shown by default, I prefer the 2.6.3 behaviour
there is a workaround here though ideally I wouldn't need to add this to every program using tesserocr to silence some debug-level messages
I tried using set_leptonica_log_level to silence this but as far as I can tell it's not possible to use this function?
>>> import tesserocr
>>> tesserocr.set_leptonica_log_level(tesserocr.LeptLogLevel.ERROR)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: Argument 'level' has incorrect type (expected tesserocr.tesserocr.LeptLogLevel, got int)
and even with that function working I would then have to require my users to upgrade tesserocr to >=2.7.0
The text was updated successfully, but these errors were encountered:
discussed a bit in #348 -- here's the separate issue
some minimal code to reproduce the problem:
prior to 2.7.0 I get no output, but after 2.7.0 I get some pretty annoying terminal spam by default:
I also get this ~sometimes on shutdown for a different program -- but I haven't been able to make a minimal reproduction of that:
I don't think either of these outputs should be shown by default, I prefer the 2.6.3 behaviour
there is a workaround here though ideally I wouldn't need to add this to every program using
tesserocr
to silence some debug-level messagesI tried using
set_leptonica_log_level
to silence this but as far as I can tell it's not possible to use this function?and even with that function working I would then have to require my users to upgrade
tesserocr
to >=2.7.0The text was updated successfully, but these errors were encountered: