-
Notifications
You must be signed in to change notification settings - Fork 16
Unhandled Exception in Async Work #105
Comments
I thought this issue might pertain to resources of different languages being synced together when those resources are not, say, English and Hebrew/Greek. As a test, I ran Targum Psalm (non-biblical Aramaic), the Targum Lexicon, and HALOT to see if this caused the issue; it did! But when I removed HALOT, the issue still happened with just the Targum Psalm and Targum Lexicon. Given I found this issue happening with the apparatuses, the Vulgate, and these Aramaic resources, I'm wondering if it has more to deal with particular resources than something else. |
I'm now also seeing this error in the library panel. I tried a two-word search "directory for" and the search ended while typing "for". A diff of the two files pasted so far does indicate these are difference issues, though the uppermost unhandled exception is the same (async work, failfast). |
I thought it'd be worthwhile pulling one of the errors out of the async error's log entry:
I wonder if this "CultureNotFoundException" is the source of the problem since it "is an invalid culture identifier". |
I managed to fix this today after a reboot failed to fix it by removing the library catalog. This would suggest to me that something happens during Logos's operation that corrupts the library catalog for us. This would go hand-in-hand with our trouble-with-first-boot issue: something is happening that causes Logos/wine to corrupt the catalog. EDIT: Today (20230720) I faced the same issue and it was also fixed by removing the library catalog. EDIT: The error surfaced soon after clearing this and I got a new async error: Note this still has the "Culture is not supported" language but the output is much longer with another error:
|
This time Logos failed and it failed with only the culture error: |
This error is likely an upstream bug, but I am going to begin collecting data on this crash for submitting a WINE bug report.
Here is a full error output:
https://pastebin.com/Y0XvDzrm
I've triggered this primarily in two situations. First, when the Text Comparison Tool is open, I found that Logos regularly crashed when the Vulgate was an included translation. Second, when working in Aramaic on one of the Targums, slowly scrolling through the text I have noticed Logos will regularly crash.
I have noticed this in other situations, such as scrolling in the BHS apparatus or hovering over one of the links in the BHS apparatus causes it, but even other more mundane situations can cause this crash.
This is the main thing which blocks my Logos on Linux use from being pleasurable. If this were solved, I don't think I'd have any major issues.
UPDATE: This is happening when I have a link set placed on one of the aforementioned resources, thus as I scroll through DBL, BDB, HALOT, or NIDOTTE, the async error can trigger for the BHS/BHS apparatus.
Given that Logos's BHS does report in the German, I'm wondering if this is some kind of problem with the fact that my interface is English but these other resources are not primary (i.e., Hebrew, Greek, Biblical Aramaic) languages (Latin, Aramaic, German) and if something is different between the languages.
The text was updated successfully, but these errors were encountered: