BUG: CRASH: Using shortcut to Close All

Don Awalt
Don Awalt Member Posts: 3,547 ✭✭✭

Verbum/Mac, v.41, was open since yesterday - i.e. open overnight (which I usually leave it up all the time). I clicked on a lectionary panel on the home page, reviewed it briefly, then did a shortcut to close all. Verbum closed out with a crash. Logs attached.

Tagged:

Comments

  • Don Awalt
    Don Awalt Member Posts: 3,547 ✭✭✭

    Hello, any acknowledgement of this crash? @Matt Mattox (Faithlife) can you help?

    BTW, it crashed again this morning - doing nothing with it, it was idle. Crash logs attached.

  • Don Awalt
    Don Awalt Member Posts: 3,547 ✭✭✭

    On restart, Indexing briefly ran. A few minutes later I opened Verbum and it froze on the splash screen. I gave it about 3 minutes, force quit it, then I opened it again, it came right up this time. Something is amiss with this release.

  • Joseph Valentine
    Joseph Valentine Member Posts: 31 ✭✭

    I am noticing a definite temporary freeze when opening my notes. The notes panel opens but is non-responsive for a few seconds. This is a definite degradation in the current version (first release of V41).

  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 1,012

    Just commenting that I saw your ping and will look into this. I'll post back once I know more.

  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 1,012

    @Don Awalt Looks like we have a fix. It should go out in a future beta release.

  • Don Awalt
    Don Awalt Member Posts: 3,547 ✭✭✭

    Thank you so much @Matt Mattox (Faithlife) !!! And that is AWESOME NEWS!!!

  • Don Awalt
    Don Awalt Member Posts: 3,547 ✭✭✭

    @Matt Mattox I got another crash this morning, this time with the new 41 service release 1 (41.1.6). I did an F5 on Verbum/Mac to refresh the Home Page, to see new panes in the Explore section, and it exited the app. MacOS/console reported it as a crash in Verbum. I did F5 about another dozen times once I restarted after I collected the log files, with no issues.

    Here are the logs, is this the same issue you said would be fixed in a future beta release?

  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 1,012

    @Don Awalt Hmm, have you ever modified your registry manually? Or are there multiple user accounts on your machine? Or are you using an admin account on the machine? I ask as so far you are the only crash and saw this article which seems related.

    I'd scroll to the cause and resolution section after you read the beginning section as the log examples are just examples of a scenario.

    The error in your stack trace:


    ---> System.IO.IOException: Illegal operation attempted on a registry key that has been marked for deletion.

  • Don Awalt
    Don Awalt Member Posts: 3,547 ✭✭✭

    HI @Matt Mattox that error is incorrect - I am on Verbum/Mac, there is no registry! So that article does not apply either. So maybe that's the problem 😎

    I am using an admin account, I always have. There are no other accounts on this laptop.

  • Dave Hooton
    Dave Hooton MVP Posts: 36,195

    It is in the Mono runtime emulating a Windows .NET environment, so not your issue!

    Dave
    ===

    Windows 11 & Android 13