Issue with v41 Update Causing Resource Crashes
Issue with v41 Update Causing Resource Crashes
I recently updated to MacOS (Ventura 13.7.5) Desktop, Logos version 41 a couple of days ago. Since then, resources containing input fields for notes either crash immediately upon opening or shortly after scrolling through them.
I’ve already worked through all the troubleshooting steps provided in the Help section, but the issue remains unresolved.
Has anyone else encountered—and successfully resolved—this issue or something similar?
Best Answer
-
@Joe Johnson This should be fixed on the latest 41.1 update.
NOTE: The fix only applies to macOS machines.0
Comments
-
Just to clarify, I'm running MacOS 13.7.5 and upgraded Logos desktop from v.38 to v.41
1 -
Same here.
0 -
Glad to hear I’m not the only one—though I wish none of us had to deal with it! Hopefully a fix is on the way soon. Thanks for confirming @William Pankey
1 -
Had a crash with Open Door on Mark on p.57, last question.
Using Logos and Verbum 41 on Windows.
Dave
===Windows 11 & Android 13
0 -
@Dave Hooton that's interesting, I just opened that resource and Logos crashes upon opening…
0 -
Does anyone have crash logs for this problem that they can upload?
0 -
I've previously uploaded a crash log (maybe 2). I was also asked to upload another log file "if the resources loaded properly"— after following the troubleshooting steps, including renaming the "documents" folder… — which the did not.
0 -
Where did you upload them? I don't see any attachments in this thread.
0 -
They were attached to a "support email" before I entered any comments/questions to the discussion forum…
0 -
Looks like I attached a single log file to the "support email" before I entered any comments/questions to the discussion forum… If you need a fresh log file just let me know…
0 -
Do you have an open support ticket where you've already been troubleshooting this problem with a support technician?
0 -
Doesn't appear to be a ticket number or case number. I opened the request via email, received a response from a "bot" and have sent it about 6-7 updates. I don't think I've received any response to the updates. That's when I found the forum and started this thread.
0 -
UPDATE:
Looks like Daniel Soto was the last support staff, he followed up on the updates I responded to in the email thread, and he gave me some instructions which didn't not resolve the issue. I see Isaac Díaz was also in the conversation…
0 -
We believe we have a fix for macOS but we'll need log files from someone on Windows to further investigate a fix that crash. @Dave Hooton are you able to upload your log files at a convenient time?
0 -
Encouraging! Thank you for the update…
1 -
Matt,
I was attempting to type an answer to the first Question on p.57 of Open Door on Mark (so this is reproducible).
There is no Logos crash log.Event Viewer:
Log Name: Application
Source: Application Error
Date: 15/04/2025 10:14:11 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Description:
Faulting application name: Logos.exe, version: 41.0.0.416, time stamp: 0x67ab0000
Faulting module name: coreclr.dll, version: 9.0.325.11113, time stamp: 0x67abd784
Exception code: 0xc0000005
Fault offset: 0x00000000002e5e04
Faulting process id: 0x20F0
Faulting application start time: 0x1DBAB4744863986
Faulting application path: E:\Logos\System\Logos.exe
Faulting module path: E:\Logos\System\coreclr.dllDave
===Windows 11 & Android 13
0 -
Thanks, I wasn't able to reproduce it on my end.
> There is no Logos crash log
Yeah, I'm not seeing anything in the logs that would indicate a crash. There usually is a stack trace towards the bottom of the logos.log file. I hate to ask this but if possible and you can repro consistently. Are you able to try again and see if your logs have any new information on the crash? It might help us too if you upload the entire log file in case there is something else going on.0 -
@Joe Johnson This should be fixed on the latest 41.1 update.
NOTE: The fix only applies to macOS machines.0 -
Matt,
I've tested 5 different resources that were previously crashing.
They all open successfully now.
Thank you!
1 -
Same crash as before on first question. Note that trying to input means nothing got entered after typing a few letters in the box.
File includes .NET run time crash. All my logs are complete. Fast crash not caught by Logos log.
Dave
===Windows 11 & Android 13
1
