CRASH moving from Beta 3 to Beta 4

1. Got the message Beta 4 was out - did the Update command, saw the message that an update would be installed on restart. I restarted.

2. I saw 4 resources from prepubs should be downloading. I did an Update resources, as they did not show up in my library yet. Logos exited out, no message or anything

I collected the logs before I restarted:

4401.Archive.zip

This is what MacOS console reported:

Process: Verbum [88950]
Path: /Applications/Verbum.app/Contents/MacOS/Verbum
Identifier: com.logos.desktop.verbum
Version: 28.0.0.27 (63900.0.27)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-08-29 19:03:51.6268 -0400
OS Version: macOS 13.5.1 (22G90)
Report Version: 12
Anonymous UUID: 90E67F60-9BD5-84F8-6F33-0CAF75A286F1

Sleep/Wake UUID: FC81543C-A2EA-4662-9E62-60BAF5B89DCE

Time Awake Since Boot: 240000 seconds
Time Since Wake: 4000 seconds

System Integrity Protection: enabled

Crashed Thread: 65 .NET ThreadPool Worker

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000017985adec

Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process: exc handler [88950]

Find more posts tagged with

Comments

Dave Hooton

I collected the logs before I restarted:

4401.Archive.zip

This appears to be associated with installing LLS:1.0.220 (paste this in the Command Box to see its title). You might try to re-download it e.g. Remove and Download (just Download if "Not on this device").

Don Awalt

https://community.logos.com/discussion/comment/1269969#Comment_1269969

Thank you Dave for checking the logs! That resource is "La Sankta Bible", which I don't use - it came in one of the Verbum 10 packages. And yes, yesterday Logos sent down some sort of update.

I only had the crash once. Before I did anything with that resource this morning, I tried opening the resource, it seemed fine. I still removed it, re-downloaded it, and re-opened it - all good.

So I guess things are fine, thanks Dave!

As a comment from a software guy, I would think a good way to reduce random crashes for users would be to put a checksum on each resource and to process accordingly if a resource gets corrupted on the download - before suffering from a crash. Maybe they don't because in some cases (like a new install), there would be a lot of extra calculations - but even that could be handled, probably. They could already be downloading resources in a compressed format, if so they are already processing the resource? Who knows :-)

It would be nice if a corrupt resource could be caught - it could be a long time from corruption to a user opening the resource (or it being processed.) Plus, catching it may offer the chance to send some diagnostic details to Logos to figure out the reason for corruption. It remains to be seen if it's being corrupted on the download, or due to some bug on either the backend or user end - a problem which may never be found otherwise.

Thanks again Dave!

Dave Hooton

https://community.logos.com/discussion/comment/1270030#Comment_1270030

As a comment from a software guy, I would think a good way to reduce random crashes for users would be to put a checksum on each resource and to process accordingly if a resource gets corrupted on the download - before suffering from a crash. Maybe they don't because in some cases (like a new install), there would be a lot of extra calculations - but even that could be handled, probably. They could already be downloading resources in a compressed format, if so they are already processing the resource? Who knows :-)

If you check the log just before the crash, you will see that an MD5 hash is being checked, which appears to be for the patch. The crash details include:

13 (wrapper managed-to-native) Libronix.DigitalLibrary.NativeMethods:PatchResource
14 Libronix.DigitalLibrary.ResourceUtility:PatchResource .....
15 LDLS4.Update.InstallResourceUpdateStage:TryApplyResourcePatch...
16 LDLS4.Update.InstallResourceUpdateStage:ProcessFinishedResourcePatch
17 LDLS4.Update.InstallResourceUpdateStage:ProcessDownloadableUpdateJob

It crashed trying to apply the patch.

Logos could have applied (another) patch after restarting.