-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
TBD: make Qiqqa cope better with flaky/damaged/b0rked PDF files #13
Comments
…ugs, first of them: jimmejardine#10, then jimmejardine#13
Done as per #33. Lots of commits related to this issue. This set surely won't cover all as I've had crashes in lots of places during testing a 20K+ library which has collected its own amount of cruft from the Internet and years of Qiqqa fails (Sniffer lockups, download b0rks due to connection failure and what-not, you-name-it 🤡 ): Revision: dc740d7 Revision: d59d6f0
Revision: bab0499 Revision: da3f853 Revision: 7bd3ee6 Revision: 53f2ca8 Revision: 5dcda97 Revision: 8a1d766 Revision: 72b8d25 Revision: b359039 Warning: I got those files by copying a Syncfusion install directory into qiqqa::/libs/ and overwriting existing files. v17 has a few more files, but those seem not to be required/used by Qiqqa, as only overwriting what was already there in the Qiqqa install directory seems to deliver a working Qiqqa tool. :phew: |
|
Now that I have access to the Qiqqa source code and have been able to rebuild the binary and extend its logging, I find that quite a lot of my troubles in the past years is due to Qiqqa not coping well with all kinds of broken/b0rked PDF files in the Qiqqa libraries:
several PDFs caused Qiqqa to run indefinitely after closing it #10: several PDFs caused Qiqqa to run indefinitely after closing it: every time I had to open the Windows Task Manager and KILL thr Qiqqa process or process tree to make it stop. If I didn't do that, Qiqqa would report it's already running when you restart it, necessitating a reboot. Instead, I've executed the Windows equivalent of
kill -9
every time I exit/stop Qiqqa.search index stops working and re-indexing doesn't recreate the Lucene search db #16: Qiqqa failed on several occasions with my large PDF collection, causing a permanent and total failure in its search feature, i.e. the Lucene database got nuked/b0rked. All subsequent searches in Qiqqa would deliver ZERO results, quickly.
Reindexing via the Qiqqa Tools panel would have no effect.
Manually deleting all the Lucene DB files in
base/Guest/index/
would also be to no avail.Reconstructing the Library by importing the PDF files in tiny batches via the Directory Watch feature of Qiqqa would result in 'semi-random behaviour': it now turns out to be highly dependent on which PDF files got loaded first: as soon as an offending PDF (to be uploaded later) got included in the library, the Lucene-backed search facility would break down and stop to function.
When using the sniffer (Yay! 😄 Superb Feature!) to fetch additional documents (PDFs), sometimes you'll observe a load failure, where
kill -9
Qiqqa to stop it. Depending on the alignment of the planets, you'll be able to restart Qiqqa with a functioning or broken 'search' feature then.Waiting on http://website/path.../file.pdf
would be shown forever in the status line at the bottom of the main window.There's no way to dig out these b0rked PDFs from the library and 'select all' the discovered culprits to apply some chosen user activity (delete PDF + library entry, export/dump to diagnostics directory, ...?what you want?...)
The text was updated successfully, but these errors were encountered: