AwesomeTTS / awesometts-anki-addon

AwesomeTTS text-to-speech add-on for Anki
GNU General Public License v3.0
484 stars 100 forks source link

AwesomeTTS make Anki remain in background processes #190

Closed davyzhu closed 3 years ago

davyzhu commented 3 years ago

To reproduce the problem:

  1. Disable other Add-ons, disable win 10 defender anti-virus
  2. Create a card and open AwesomeTTS, record a mp3 file
  3. Close Anki by Click up-right corner cross. Anki will remain in background processes.
  4. Reopen Anki, it will show up but have no response, and setting icon(gear) don’t display properly

Environment: Win 10 Anki 2.1.42(or 2.1.41) AwesomeTTS 1.34.0

tts3 tts1 tts2 tts4 tts5 tts6

davyzhu commented 3 years ago

I have simplify it by suggestion from dae:

  1. Open Anki, Enable AwesomeTTS
  2. Click “add”, Click AwesomeTTS Icon, Don’t have to create mp3, close AwesomeTTS
  3. Disable all add-ons, Close Anki
  4. Find mpv in Task Manager and terminate it
  5. Reopen Anki, problem still exist
luc-vocab commented 3 years ago

I'm having trouble reproducing these steps, I can generate audio on AwesomeTTS and it doesn't prevent Anki from closing. Is that the first symptom - Anki not closing ?

davyzhu commented 3 years ago

Anki is running after I close it by click right corner cross. And, yes, this happen regardless of which service I use. Actually, I just open AwesomeTTS and close it, don’t have to create audio file.

Before I open AwesomeTTS, Anki’s CPU usage is about 1%. After I open AwesomeTTS, Anki’s CPU usage increase to 16%. I have a 6 logical core CPU, so I guess AwesomeTTS run into some kind of infinite loop and eat up one logical core. Then I close Anki, and after a few minutes, it’s still running, CPU usage is about 16%, see screenshot.

image

luc-vocab commented 3 years ago

I'm able to reproduce this now, a mandatory step is to start up AwesomeTTS from the button in the editor.

luc-vocab commented 3 years ago

@davyzhu please get in touch with me awesometts@airpost.net , i want to send you a reward for reporting this bug.