Qiqqa crashing - out of memory error when Qiqqa (v.81s/v82 on Windows) crashes #281
Comments
|
@danieleboaretti Moved your comment to a new issue to keep the original issue very focused. You can email me your Qiqqa logfiles (zipped, please) to ger at hobbelt.com with a email subject line mentioning both Qiqqa and this issue number at least so the spam filters will be able to decide properly. 😉 For guidance about collecting the logfiles, the comments in #264 are hopefully sufficient to make that a doable task. I'm still swamped with RL stuff, so please do not expect an answer before the new year has arrived (this weekend); ring the 🛎️ here in the issue tracker if I'm even slower than that. Oh, and please mention in this issue that you've sent me an email with log files, thanks! 👍 |
|
@GerHobbelt I have just sent you the zip file, please let me know if you have received the email, it should be compliant with your instructions 😄 |
|
HMMM, that one didn't make it through. Also not in spam box.
Did you zip the log file(s)? Email is generally limited to attachments
which are not larger than ~ 10 MByte; sending logfiles as-they-are can be
too large for email.
Alternative is email a link to a Google Drive or DropBox or other 'cloud
storage' where I can fetch the logfiles. ZIPping files can be done using,
for example, open source archivers such as 7zip: https://www.7-zip.org/
Met vriendelijke groeten / Best regards,
Ger Hobbelt
…--------------------------------------------------
web: http://www.hobbelt.com/
http://www.hebbut.net/
mail: [email protected]
mobile: +31-6-11 120 978
--------------------------------------------------
On Tue, Dec 29, 2020 at 12:45 PM danieleboaretti ***@***.***> wrote:
@GerHobbelt <https://github.com/GerHobbelt> I have just sent you the zip
file, please let me know if you have received the email, it should be
compliant with your instructions 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#281 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADCIHTOJNRP5GAYH4655SLSXG6NLANCNFSM4VNDJ5LQ>
.
|
|
I apologize for that, The email app did not work as expected. I have just sent you the email. I checked and it has been delivered. |
GerHobbelt
changed the title
…f the culprits it seems. Added memory status report code to dump into the logging as the GC output is not reliable when we want to know how much memory was actually used at the peak, when the OutOfMemory exception happened. - lots of CultureInfo.CurrentCulture params are not necessary and only make the code harder to read. Removed where MSVC2019 doesn't yak about these any more. - added *reason* message for logging lines which report when Qiqqa is being shut down. This should help diagnose jimmejardine#280 / jimmejardine#281 as well. - tweaked the exit process to track and report the total number of threads running as well as only the SafeThreadPool - document comments for several routines re LDA and AutoTag creation. Finally understanding how it's done. The LDA is *not* used for creating the AutoTags but only to find the *commonly shared* tags when running in Expedition. The BuzzwordGenerator is the AutoTag generator (in combination with some other code) and is using some plain basic heuristics. autoTags are extracted from the *document title* only, which explains the lousy AutoTag performance I got with the latest lib, as that one has very few PDFs which pass through OCR unscathed.
|
@danieleboaretti : Quick heads up: new release to try: https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v83.0.7655.37537 Please report anything you observe with the new release. Thanks! |
|
@danieleboaretti : Quick heads up: hotfix release to try: https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v83.0.7656.6401 (which fixes known issue in previous release https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v83.0.7655.37537) Please report anything you observe with the new release. Thanks! |
…I thread; the lib uses COM under the hood, which requires a working and accessible Windows message pipe, something which only the UI thread can provide. - littered the code with WPFDoEvents UI/not-UI assertions -- which caught the above scenario in a Dispose() for a page image render. And that was the hint the needed to progress a little further towards stibility: it was SORAX which caused a *lot* of the out-of-memory failures due to crazy COM/WPF/UI failures, even for smaller libraries under test. - fix bit of an odd crash in the Lucene flush/cleanup during shutdown, where Lucene kept busy with 'optimizing the index' while a quick application termination was happening in the background, resulting in lockup and then a crash. - this MAY be a fix for the reported "number of documents reported not matching reality": added update/refresh code to update the library list panel when PDF documents are added in the background via FolderWatcher or other means (async library loading). WARNING: this code is still incomplete/buggy! - most UI assertions have been covered now. Keeping them anyway as this is hairy stuff and should be tested more. Addresses (but is not guaranteed to fix) jimmejardine#290, jimmejardine#283, jimmejardine#281, jimmejardine#280, jimmejardine#243
I am also interested in this issue. In the log files, I have an out of memory error which I believe occurs when Qiqqa (v.81s on Windows) crashes.
This is the most relevant part from the log:
If needed, I can also send an email with the Log folder as zip file.
Originally posted by @danieleboaretti in #264 (comment)
The text was updated successfully, but these errors were encountered: