Another Verbum Indexer crash

Maybe I caught this one in time.....I had Verbum running overnight as I always do. It was in its own Window on the Mac. I was working in another Window, and I shut down all the apps to restart the laptop. When it came back up, just on a whim I checked the Mac console Crash reports, and there it was, from this morning. So it may be shut down is causing it to crash. Here is what the Crash Report said, and my logs are attached below. I hope you can find something!

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: BC9151A3-A0E2-4CD5-A6BE-6EC2D680CA31
CrashReporter Key: 90E67F60-9BD5-84F8-6F33-0CAF75A286F1
Hardware Model: Mac14,6
Process: VerbumIndexer [655]
Path: /Applications/Verbum.app/Contents/Frameworks/FaithlifeDesktop.framework/Versions/23.0.0.28/Frameworks/ApplicationBundle.framework/Versions/A/VerbumIndexer.app/Contents/MacOS/VerbumIndexer
Identifier: com.logos.desktop.verbumindexer
Version: 23.0.0.28 (63400.0.28)
Code Type: ARM-64 (Native)
Role: Unspecified
Parent Process: launchd [1]
Coalition: com.logos.VerbumIndexer [767]

Date/Time: 2023-02-11 07:12:44.3599 -0500
Launch Time: 2023-02-11 07:12:41.7141 -0500
OS Version: macOS 13.2 (22D49)
Release Type: User
Report Version: 104

Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: CODESIGNING 4 Launch Constraint Violation

Highlighted by Thread: 0

Backtrace not available

No thread state (register information) available

Binary Images:
Binary images description not available

Error Formulating Crash Report:
_dyld_process_info_create failed with 30
dyld_process_snapshot_get_shared_cache failed
Failed to create CSSymbolicatorRef - corpse still valid ¯\_(ツ)_/¯
thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

EOF

8625.Archive.zip

Find more posts tagged with

Comments

Don Awalt

Some additional notes that may be important - I just discovered on restart, that it started indexing. I found that two prepubs downloaded, I guess overnight. So maybe it was the combination of unattended prepub downloads and a quit that caused the crash?

Dave Hooton

https://community.logos.com/discussion/comment/1246752#Comment_1246752

I found that two prepubs downloaded, I guess overnight. So maybe it was the combination of unattended prepub downloads and a quit that caused the crash?

The sequence is similar to the first as there is not Indexer log or error log for the console 'crash'.

Do the 2x prepubs produce results in a Search?

Don Awalt

https://community.logos.com/discussion/comment/1246819#Comment_1246819

The two resources search fine. I just noticed another crash this morning - I am pretty sure it's happening on a system induced restart, as I did one this morning (Apple logo/Restart). This is the console log, and logs are below:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: 685CF15F-444A-428F-AFDF-2FAD03EEA83D
CrashReporter Key: 90E67F60-9BD5-84F8-6F33-0CAF75A286F1
Hardware Model: Mac14,6
Process: VerbumIndexer [1007]
Path: /Applications/Verbum.app/Contents/Frameworks/FaithlifeDesktop.framework/Versions/23.0.0.28/Frameworks/ApplicationBundle.framework/Versions/A/VerbumIndexer.app/Contents/MacOS/VerbumIndexer
Identifier: com.logos.desktop.verbumindexer
Version: 23.0.0.28 (63400.0.28)
Code Type: ARM-64 (Native)
Role: Unspecified
Parent Process: launchd [1]
Coalition: com.logos.VerbumIndexer [1066]

Date/Time: 2023-02-12 07:07:53.5582 -0500
Launch Time: 2023-02-12 07:07:53.4417 -0500
OS Version: macOS 13.2 (22D49)
Release Type: User
Report Version: 104

Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: CODESIGNING 4 Launch Constraint Violation

Highlighted by Thread: 0

Backtrace not available

No thread state (register information) available

Binary Images:
Binary images description not available

3058.Archive.zip

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/1246836#Comment_1246836

The two resources search fine. I just noticed another crash this morning - I am pretty sure it's happening on a system induced restart, as I did one this morning (Apple logo/Restart).

Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid))

Signal to Kill (SIGKILL) process(es) is consistent with a system induced restart. SIGKILL indicates macOS terminated the process.

Keep Smiling [:)]

Dave Hooton

https://community.logos.com/discussion/comment/1246839#Comment_1246839

The two resources search fine

Signal to Kill (SIGKILL) process(es) is consistent with a system induced restart.

Which means the resources were indexed despite a "system induced restart" (where the available log confirmed there were no books to index)!

The only way to see the original indexing is to change your Setting for Automatically Start Downloads to NO (and keep Download New Resources = YES). After you start the download, monitor the indexer progress and save the logs occasionally. Note how far it got (e.g. 97%) and if indexing was resumed. Upload the last set you saved for the original indexing.

Don Awalt

https://community.logos.com/discussion/comment/1246879#Comment_1246879

On the Mac you get a Verbum 'V' icon on the menu bar, so it's really obvious when it's indexing (unless you turn it off of course). To my knowledge all indexing in recent times have completed to 100% perfectly. This is happening when there is not any indexing going on. This morning's crash was long after those 2 resources came down.

Dave Hooton

https://community.logos.com/discussion/comment/1246885#Comment_1246885

Don,

If you are happy that "to my knowledge all indexing in recent times have completed to 100% perfectly" then we can close this case with the mysterious Mac console crash/restart. But is it true that you allow Downloading to occur at any time, because the indexing that follows is the real indexing that should show in the logs, except that it is being overwritten by a subsequent log that says no books need to be indexed!

Don Awalt

https://community.logos.com/discussion/comment/1246896#Comment_1246896

Hi Dave, all indexing is working fine from every test I can throw at it. I am 99% sure this is a crash that happens when the Mac/Ventura is restarted. I have now duplicated it 3 times, and this last time there was no indexing going on in the last day (of resources; of course it was running and who knows what it does in idle state, if anything).

I do think this crash is easy to duplicate. Verbum/Mac, have Verbum running, Restart the Mac (via 'Apple" in top left corner/Restart). Indexer Crash every time.

Matt Mattox

https://community.logos.com/discussion/comment/1246933#Comment_1246933

I do think this crash is easy to duplicate. Verbum/Mac, have Verbum running, Restart the Mac (via 'Apple" in top left corner/Restart). Indexer Crash every time.

Can you elaborate a bit on the steps. At what point do I need to restart my mac? Is the indexer still running or is it just finishing?

Don Awalt

https://community.logos.com/discussion/comment/1246979#Comment_1246979

HI Matt, I don't think either. The last three mornings I sat down at my Mac, and it was on/sleeping all night. Verbum ran all night. Nothing downloaded or indexed, so everything was pretty quiet on the Verbum and Indexer front. I restarted my Mac for a different reason, and that is what caused the crash. It definitely is not in the middle of an indexing operation or anything. I hope that helps!

Matt Mattox

https://community.logos.com/discussion/comment/1246991#Comment_1246991

That is helpful, might be hard to replicate on my end since no real action was taking place inside the application. If you end up doing some steps in Verbum while the crash happens, post back here with some details.

Matt Mattox

https://community.logos.com/discussion/comment/1246991#Comment_1246991

Don Awalt

https://community.logos.com/discussion/comment/1247073#Comment_1247073

Matt, why not just try letting Verbum/Mac idle for a few hours (feel free to use the Mac or not, since it's happened both overnight and during the day), then restart the Mac?

Matt Mattox

https://community.logos.com/discussion/comment/1247092#Comment_1247092

Yeah I can give that a shot. I'm using a virtual machine so not sure how that idle part handles. I'll let my mac application run over night. When I get back I'll reboot.

Don Awalt

https://community.logos.com/discussion/comment/1247144#Comment_1247144

It just doesn't seem to matter - I just did this. I had a prepub come down, it was at 2% indexing. I paused for 4 hours, then restarted. Indexer crash after I restarted. If doing this in a VM doesn't;t work, you should really try and test this on a real Mac - it happens every single time for me; and it never used to (I check my crash logs pretty regularly).

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/1247144#Comment_1247144

Yeah I can give that a shot. I'm using a virtual machine so not sure how that idle part handles. I'll let my mac application run over night. When I get back I'll reboot.

Suggest starting restart inside virtual machine.

FWIW: I seem to remember some virtual machine managers effectively powered off virtual machine so process(es) inside the virtual machine did not have time to write a signal kill crash report.

Keep Smiling [:)]

Matt Mattox

https://community.logos.com/discussion/comment/1247153#Comment_1247153

Okay, trying again not on a vm.

So I got my index up and wait a few minutes and just restart my mac and I should get my application to crash?

Don Awalt

https://community.logos.com/discussion/comment/1247383#Comment_1247383

It's not the application crash, it's the indexer that crashes. The indexer can either be paused or not doing anything. With the app still up, Click the Apple logo top left, then restart.

When it's back up, run the console app, check Crash Reports in the left panel, and see if it reported a Verbum Indexer crash.

Matt Mattox

https://community.logos.com/discussion/comment/1247406#Comment_1247406

Ah I see, i'll keep investigating and get a case going. In the meantime, can you hold off on restarting your machine while your application is up and has the indexer paused?

Don Awalt

https://community.logos.com/discussion/comment/1247493#Comment_1247493

OK. But the Indexer is not paused. It is quiet, and there is nothing to index right now.