Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memory leak with stt.py #58

Open
tensorfoo opened this issue Jul 17, 2021 · 1 comment
Open

memory leak with stt.py #58

tensorfoo opened this issue Jul 17, 2021 · 1 comment

Comments

@tensorfoo
Copy link

tensorfoo commented Jul 17, 2021

Hi, If you do an inference with a Transcriber object t.transcribe(..), after returning the result, it should release any resources related to that inference. But it stays on VRAM and after a few calls to t.transcribe(), I get CUDA related out of memory errors. Looking at nvidia-smi it shows the memory is still occupied even after the transcript has been returned.

It would be nice to have a long lived Transcriber object which can be reused avoiding the lengthy creation time. If you're busy please give me a hint on how it may be done so I can give it a shot and submit a PR. Thanks for your project.

@EdenJin20171503024
Copy link

hi, I have the same problem, have you slove it?

Hi, If you do an inference with a Transcriber object t.transcribe(..), after returning the result, it should release any resources related to that inference. But it stays on VRAM and after a few calls to t.transcribe(), I get CUDA related out of memory errors. Looking at nvidia-smi it shows the memory is still occupied even after the transcript has been returned.

It would be nice to have a long lived Transcriber object which can be reused avoiding the lengthy creation time. If you're busy please give me a hint on how it may be done so I can give it a shot and submit a PR. Thanks for your project.

HI I have the same problem, have you slove it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants