BUG Unceremonious crash after using Hymnal

2235.LogosLogs.mikebinks.20220220-115400.zip

After testing the Hymnal resource I moved back to the forums with the aim of replying to the thread about the Hymnal being slow.

After a couple of seconds Logos crashed and reported...

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

Process: Logos [9439]
Path: /Applications/Logos.app/Contents/MacOS/Logos
Identifier: com.logos.Logos
Version: 9.11.0.22 (62011.0.22)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2022-02-20 11:53:08.5072 +0000
OS Version: macOS 12.2.1 (21D62)
Report Version: 12
Anonymous UUID: 399BBFFD-15A1-7E31-E9A9-8F84DBCC61FA

Sleep/Wake UUID: C78C037B-D847-4095-AB3D-5A324CAE7126

Time Awake Since Boot: 150000 seconds
Time Since Wake: 97940 seconds

System Integrity Protection: enabled

Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Codes: 0x0000000000000001, 0x0000000000000018
Exception Note: EXC_CORPSE_NOTIFY

VM Region Info: 0x18 is not in any region. Bytes before following region: 4334657512
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 1025da000-1025dd000 [ 12K] r-x/r-x SM=COW ...s/MacOS/Logos

Application Specific Information:
abort() called

Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - Fault hit memory shortage
VM - Fault hit memory shortage
VM - Compressor failed a blocking pager_get

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 ??? 0x7ff89f20a940 ???
1 libsystem_kernel.dylib 0x7ff80ec44112 __pthread_kill + 10
2 libsystem_c.dylib 0x7ff80ebc6d10 abort + 123
3 libmonosgen-2.0.1.dylib 0x11829df9e mono_post_native_crash_handler + 14
4 libmonosgen-2.0.1.dylib 0x11823a124 mono_handle_native_crash + 468
5 libmonosgen-2.0.1.dylib 0x1181986f2 mono_sigsegv_signal_handler_debug + 514
6 libsystem_platform.dylib 0x7ff80ec8fe2d _sigtramp + 29
7 AppKit 0x7ff8116bb149 -[_NSInternalNotificationCenter postNotification:] + 123
8 ??? 0x0 ???
9 ??? 0x1 ???
10 ??? 0x0 ???
11 ??? 0x0 ???
12 ??? 0x7ff85040ae48 OBJC_METACLASS_$_NSObject + 40
13 ??? 0x7ff85040ae48 OBJC_METACLASS_$_NSObject + 40

etc

Find more posts tagged with

Desktop App

Comments

Maria

Oh, thank you for testing this Mike!!

(It's my post about the slow hymnal that you referred to, I think.)

I'm very grateful to you for posting so much detail, so that Logos knows what is going on.

Maria

Dave Hooton

After testing the Hymnal resource I moved back to the forums with the aim of replying to the thread about the Hymnal being slow.

I didn't find it slow but I consigned it to the bottomless pit!

After a couple of seconds Logos crashed and reported...

Weird, after a lot of carrying on just to get it downloaded the crash occurred whilst indexing of the Hymnal was in its last stages.

Did you attempt to access it after restarting the computer?

Mike Binks

https://community.logos.com/discussion/comment/1197454#Comment_1197454

Did you attempt to access it after restarting the computer?

No. I wasn't that interested. One crash was enough for me; and one too many for the developers I should hope.

Anyway I am always wary of the adage

'One definition of insanity is repeating the same thing and expecting a different result'

Philana R. Crouch

Mike,

I've been trying to reproduce this crash. Are you able to reproduce this consistently? If so, could you post steps or even a video recording? I've tested this on both macOS Big Sur and Monterey and I'm not experiencing any performance or crashing issues. Do you have an M1 chip?

Maria

https://community.logos.com/discussion/comment/1197496#Comment_1197496

7127.Logos.zip

If I followed directions correctly, these are the logs after mine crashed.

I had a layout with several tabs (maybe 5) open. I opened the hymnal. Then I started exploring in the other tabs - opening a commentary, clicking on a different verse, etc. Reactions to my clicks slowed, then stopped. When I clicked on something after Logos stopped responding, Logos crashed. (But not my computer - is that still called a crash?)

I re-opened Logos and followed the directions to get the logs.

Unfortunately, all my posts are being sent for moderation, so this post here may not show up here for a day or two.

I'm sincerely grateful to each of you for the help you gave in bringing attention to this. I love the hymnal, and would love to add it to my daily devotions layout, if this can be fixed.

Maria

https://community.logos.com/discussion/comment/1197496#Comment_1197496

I forgot to say...I am able to recreate the problem consistently.

It happens every time I open the hymnal with many other tabs open (maybe 5 or more), if I continue to work in those tabs or open new tabs while the hymnal is still open. Even trying to close the hymnal will then create a problem.

Thank you again!

Mike Binks

https://community.logos.com/discussion/comment/1197496#Comment_1197496

Are you able to reproduce this consistently?

It would seem so. :-(

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

Process: Logos [24248]
Path: /Applications/Logos.app/Contents/MacOS/Logos
Identifier: com.logos.Logos
Version: 9.11.0.22 (62011.0.22)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2022-02-22 08:19:25.6476 +0000
OS Version: macOS 12.2.1 (21D62)
Report Version: 12
Anonymous UUID: 399BBFFD-15A1-7E31-E9A9-8F84DBCC61FA

Sleep/Wake UUID: C78C037B-D847-4095-AB3D-5A324CAE7126

Time Awake Since Boot: 310000 seconds
Time Since Wake: 257917 seconds

System Integrity Protection: enabled

Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGABRT)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
Crashing on exception: Cannot remove an observer <NSEditableBinder 0x7fa05db7edc0> for the key path "resourceController.isEmbedded" from <MediaResourceImageArticleController 0x7fa05cf20e90>, most likely because the value for the key "resourceController" has changed without an appropriate KVO notification being sent. Check the KVO-compliance of the MediaResourceImageArticleController class.
abort() called

Application Specific Backtrace 0:
0 CoreFoundation 0x00007ff80edbb6cb __exceptionPreprocess + 242
1 libobjc.A.dylib 0x00007ff80eb1ddce objc_exception_throw + 48
2 Foundation 0x00007ff80faf20fa -[NSKeyValueNestedProperty object:didRemoveObservance:recurse:] + 706
3 Foundation 0x00007ff80fac0f7d -[NSKeyValueUnnestedProperty object:didRemoveObservance:recurse:] + 219
4 Foundation 0x00007ff80fac0905 -[NSObject(NSKeyValueObserverRegistration) _removeObserver:forProperty:] + 242
5 Foundation 0x00007ff80fac07cf -[NSObject(NSKeyValueObserverRegistration) removeObserver:forKeyPath:] + 129
6 AppKit 0x00007ff81167cd99 -[NSBinder _updateObservingRegistration:] + 586
7 AppKit 0x00007ff811a16184 -[NSBinder releaseConnectionWithSynchronizePeerBinders:] + 37
8 AppKit 0x00007ff81167224d -[NSObject(_NSBindingAdaptorAccess) _releaseBindingAdaptor] + 159
9 AppKit 0x00007ff8116e3608 -[NSView _releaseBindingAdaptor] + 55
10 AppKit 0x00007ff8116e1c27 -[NSView _finalize] + 1497
11 AppKit 0x00007ff8116e1516 -[NSView dealloc] + 119
12 LayoutKit 0x000000011841b407 -[Panel dealloc] + 497
13 libobjc.A.dylib 0x00007ff80eb1541f _ZN19AutoreleasePoolPage12releaseUntilEPP11objc_object + 167
14 libobjc.A.dylib 0x00007ff80eb123a0 objc_autoreleasePoolPop + 161
15 CoreFoundation 0x00007ff80ed02680 _CFAutoreleasePoolPop + 22
16 Foundation 0x00007ff80fa9ff68 -[NSAutoreleasePool drain] + 133
17 AppKit 0x00007ff81168594b -[NSApplication run] + 636
18 Logos 0x0000000104eecaee DesktopApplicationMain + 1426
19 Logos 0x0000000104eecbea main + 9
20 dyld 0x0000000204ffb4fe start + 462
21 ??? 0x0000000000000003 0x0 + 3

Do you have an M1 chip?

I do.