several PDFs caused Qiqqa to run indefinitely after closing it #10
Comments
…ugs, first of them: jimmejardine#10, then jimmejardine#13
… locks being applied correctly and completely. Also contains a few lines from work done before related to jimmejardine#10 et al.
…ose to either import a large number of PDF files at once via the Watch Folder feature *or* have just reset the Watch Directory before exiting Qiqqa, you'll otherwise end up with a long running process where many/all files in the Watched Directories are inspected and possibly imported: this is undesirable when the user has decided Qiqqa should terminate (by clicking close-window or Alt-F4 keyboard shortcut).
GerHobbelt
changed the title
|
Done as per #33. This really is a culmination of #17, #11, #13 (in particular!), #20 and other unlisted work. It still MAY happen that Qiqqa + QiqqaOCR are lingering after close when you've just clicked/imported several PDFs via Qiqqa Sniffer as Qiqqa MUST wait for QiqqaOCR to finish the (small) OCR batch it was handed. As James Jardine already noted (possibly quite long ago) in the sources, QiqqaOCR was a then-quick-hack to circumvent unsolvable issues with Tesseract and memory leaks, so this will only improve once we are able to embrace Hong Kong, pardon, Tesseract 🤡 into the Mother Mainland. That's what #37 is meant for. |
|
GerHobbelt
added
🐛bug
GerHobbelt
changed the title
The only remedy is to reboot or
kill -9Qiqqa et al, i.e. open the Windows Task Manager as Adminstrator and end all Qiqqa processes. ('end process tree')The text was updated successfully, but these errors were encountered: