"Unexpected problem in Qiqqa" (randomly) during a quick scrolling or zooming a pdf #280
Comments
|
Could you please check if this issue persists in the latest public release? (Which is available for download here: https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v82.0.7568-29227 )
|
|
@GerHobbelt Thank you for your answer! Personally, I'm not understanding the difference between the different versions of Qiqqa. Thanks! |
|
Sorry for the "pre-releases" vagueness... That's me 'signalling' that these releases haven't been tested as thoroughly as I'ld like for a true "production release" as it is known in the industry. As for "beta", "alpha", "pre-release", etc.: IMHO that's all different marketing words for the same thing: "here's the latest stuff that we're *at least somewhat confident about, but please don't be surprised if you get magical fireworks in some places". In the case of Qiqqa, after a year+ of work on it, truth is I have more confidence in my "pre-releases" than in the last v80 "release" which is commercial Qiqqa v79 with the Qiqqa Cloud access stripped out -- at least for me, v80 is riddled with troublesome issues, some of which have been addressed by the v82 releases so that many of the PDFs one can obtain through the Internet and elsewhere don't immediately cause havoc. (Application-wise, there's still the daunting upgrade paths to do: (#215), #209, #34, #35, #23, #2, #3, #225, #155, #113)
Anyhoo, the latest release I'ld advise anyone to use would indeed be build 29227: https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v82.0.7568-29227 aka v82pre11. Thanks for asking that question as it pointed me at my own worrying-about-what-is-a-good-Qiqqa-release and assumed quality standards vs. geeky stuff like semantic versioning. Bottom line for now, from a user perspective AFAICT: Which Qiqqa releases are safe to use?All of them (v82*, v81*, v80, commercial v79). If you install one and it crashes = fails to work for you, you can take any other Qiqqa release in the v82 - v79 range and install it over the existing one. Your libraries will be usable by any version since v79. Which Qiqqa release is advised?Generally 'the latest', unless there's some very specific reason mentioned for the release. At the time of writing that would be build 29227: https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v82.0.7568-29227 aka v82pre11. Counter examples?!Examples of such 'not for the general public' releases are
as these target specific users and their problems, hence these are specifically targeted problem diagnosing / solving releases, which are expected not to give a smooth user experience throughout as they are focused on problem-solving: this software is like having a plumber around in your house: I'm fine with it if you are 😄 but generally one wants the guy (and the problem he's here to fix) gone, unless, perhaps, you're married to him. 😉 You get the drift: you can use this software without harm, but you might experience more diagnostic dialog boxes and larger logfiles or other 'developer stuff happening' than you would tolerate, perhaps. @nikilito I hope this helps clear up the mist around the Qiqqa releases. Again thanks for asking as you may notice this is still a process -- which has come to a conclusion today, thanks to your asking. (To be acted on with the next 'for the general public'' release.) |
|
Thank you very much @GerHobbelt! I've been using Qiqqa for a while now and there is no other free reference manager like it: seriously. It has everything you need. Since I personally believe in the future of this project is it possible to propose small improvements? Is there a special section for this or do you always write a new "issue"? Thanks again for this super powerful program! |
|
is it possible to propose small improvements? Is there a special section
for this or do you always write a new "issue"?
Always file a new 'issue' please. As you can see in the github web
interface, these are then tagged as 'bug', 'feature', etc. when I have read
them; one can also use the github issue tracker web interface to filter on
these tags, e.g.
https://github.com/jimmejardine/qiqqa-open-source/issues?q=is%3Aissue+is%3Aopen+label%3A%F0%9F%90%9Bbug
by clicking on the red 'bug' tag in the issue list at
https://github.com/jimmejardine/qiqqa-open-source/issues
Met vriendelijke groeten / Best regards,
Ger Hobbelt
…--------------------------------------------------
web: http://www.hobbelt.com/
http://www.hebbut.net/
mail: ger@hobbelt.com
mobile: +31-6-11 120 978
--------------------------------------------------
On Tue, Dec 29, 2020 at 2:44 PM nikilito ***@***.***> wrote:
Thank you very much @GerHobbelt <https://github.com/GerHobbelt>!
Now it's clear!
I've been using Qiqqa for a while now and there is no other free reference
manager like it: seriously. It has everything you need.
A few bugs here and there doesn't kill the desire to use it.
Since I personally believe in the future of this project is it possible to
propose small improvements? Is there a special section for this or do you
always write a new "issue"?
Thanks again for this super powerful program!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#280 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADCIHXA37GBY4LRKYV6R6DSXHMLZANCNFSM4VMKIOUA>
.
|
|
Thank you Ger! Anyway, the problem persists! Now without error window: it stops working and closes without any warning! |
|
Does this happen with a particular PDF?
Can you email me a ZIPped collection of your logfiles. Maybe there's
something in there that might give a hint.
For guidance about collecting the logfiles, the comments in #264
<#264> are
hopefully sufficient to make that a doable task.
Met vriendelijke groeten / Best regards,
Ger Hobbelt
…--------------------------------------------------
web: http://www.hobbelt.com/
http://www.hebbut.net/
mail: ger@hobbelt.com
mobile: +31-6-11 120 978
--------------------------------------------------
On Wed, Dec 30, 2020 at 12:42 PM nikilito ***@***.***> wrote:
Thank you Ger!
Anyway, the problem persists! Now without error window: it stops working
and closes without any warning!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#280 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADCIHTQ6QPC7JKITGTE7TTSXMGY5ANCNFSM4VMKIOUA>
.
|
|
Also when it happens for particular PDFs only, I'm interested in a copy of
that/those PDF(s).
Met vriendelijke groeten / Best regards,
Ger Hobbelt
…--------------------------------------------------
web: http://www.hobbelt.com/
http://www.hebbut.net/
mail: ger@hobbelt.com
mobile: +31-6-11 120 978
--------------------------------------------------
On Wed, Dec 30, 2020 at 2:08 PM Ger Hobbelt ***@***.***> wrote:
Does this happen with a particular PDF?
Can you email me a ZIPped collection of your logfiles. Maybe there's
something in there that might give a hint.
For guidance about collecting the logfiles, the comments in #264
<#264> are
hopefully sufficient to make that a doable task.
Met vriendelijke groeten / Best regards,
Ger Hobbelt
--------------------------------------------------
web: http://www.hobbelt.com/
http://www.hebbut.net/
mail: ***@***.***
mobile: +31-6-11 120 978
--------------------------------------------------
On Wed, Dec 30, 2020 at 12:42 PM nikilito ***@***.***>
wrote:
> Thank you Ger!
>
> Anyway, the problem persists! Now without error window: it stops working
> and closes without any warning!
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#280 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AADCIHTQ6QPC7JKITGTE7TTSXMGY5ANCNFSM4VMKIOUA>
> .
>
|
|
No, it happens with different PDF! Logs sent! |
|
A quick look at the logs didn't uncover anything special yet, BUT I did have a suspicion, given that it happened while rendering arbitrary PDFs. After a while I got something similar to your issue (these rendering and outofmemory issues are hard to reproduce precisely anyway); at least over here the effect is the same after some "wild scrolling": a fatal Qiqqa error and termination:
That's a screenshot of the memory consumption by the qiqqa .NET code in DevStudio just after the crash and before Qiqqa ultimately dies on me: the "wild scrolling" caused the memory usage to go up to about/over 1.5GB (which is an important ceiling for 32-bit .NET applications), resulting in an out-of-memory failure fired by the SORAX PDF page rendering library:
The SORAX code will not recover from this; on another test run it locked up the Qiqqa application instead of mere crashing the app, after which I had to kill the application by hand. Sounds like it's number #280! 🤡 The important bit: what can we do about it?😭 Not much. Not right now anyway. SORAX is a discontinued commercial library (issue 209 & comment) and while preliminary work has been done to find and integrate a viable alternative (MuPDF; work on it happens here: https://github.com/GerHobbelt/mupdf), it will take a while before SORAX is finally gone. And... this 1.5GB ceiling? What if I've got 16+GB RAM? 🥳For anyone who noted that line about 32-bit and 1.5GB: tough luck for now. Qiqqa is currently limited to 32-bit builds because of the use of SORAX and, as important!, the old Mozilla XULrunner 3.x library, which is only available for 32bit .NET. The XULrunner stuff is used for the "embedded web browser" which makes the Qiqqa Sniffer do what it does and that one comes with yet another set of issues that I'ld rather get rid of, but upgrading that one to CEF/CEFSharp/YouNameEm is also no sine cure: issue tracker::xulrunner & issue tracker::sniffer tell that story. Of course, if anyone wants to pitch in and help out with migrating the code, welcome! 😉 More info in-depth:
|
…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.
|
Thank you very much Ger! Nice job! So, it will be better to scroll gently for now.... :) |
|
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! |
|
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! |
|
Hi Ger! Thanks for this new release! In the first case, the window opens, shows the error, the logs and once I close it Qiqqa closes as well. Here some details: Exception tree: Recent Logs: |
…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
…le updated: -q quiet mode patches, ...) Going to use binary PNG transmission over stdout as working with a temporary file would quickly wear out any SSD serving as temp disk: one image rendered for every page, thumbnail of a page, etc.etc.: that's a lot of images rendered and saved to temp disk space if we used that as intermediate storage. :-( - adding width next to height as a render criterium: this should ultimately fix a long-standing problem I have with Qiqqa rendering 'PowerPoint presentation PDFs' in a crazy way: those pages SHOULD be fitted to the screen as well as all other pages. That's about jimmejardine#7, jimmejardine#9, jimmejardine#209, jimmejardine#280 and a part of the work towards jimmejardine#289
Hi.
I had an "unexpected problem in Qiqqa" but the dialogue box shows nothing: completely blank.
If I go over with the pointer, I can see that there are links and text because the pointer changes.
The only solution is to kill the process from the task manager.
It happens sometimes during a quick scroll/zoom on a pdf.
If it helps:
Windows 10 Home 64 bits
Build: 19041.685
Qiqqa version v.80s
Thanks!
The text was updated successfully, but these errors were encountered: