BUG: Isn't it time Logos fixed this request?

Jack Caviness
Jack Caviness MVP Posts: 13,491
edited November 20 in English Forum

5.2a SR-3 Mac OS 10.9.2

Every time Logos starts up, the app requests a crash report even though it had experienced a normal shut down.

Tom Philpot reported the cause several weeks ago. Why has this not been fixed?

Comments

  • LimJK
    LimJK Member Posts: 1,068

    Jack,

    +1 I can confirm this, I am getting this each time I start / restart Logos for about a week.

    JK

    MacBookPro Retina 15" Late 2013 2.6GHz RAM:16GB SSD:500GB macOS Sierra 10.12.3 | iPhone 7 Plus iOS 10.2.1

  • Pascal Grosjean
    Pascal Grosjean Member Posts: 1 ✭✭

    Same thing with my Mac ...

    I quit Logos normally, the next day when I start up, it brings a crash report for no reason...

    But there seems to be nothing else, just this crash report, Logos is running ok... so let's live with it for a while and wait until Logos was able to fix this issue...

    Thank you very much

  • Tom Philpot
    Tom Philpot Member Posts: 69 ✭✭

    Jack,

    It appears that the normal "Shutting down" window that L5 Mac displays when you quit sometimes generates a ".hang" report because the app is waiting for background work/network connections to finish up. That ".hang" file is detected and reported to our crash server which explains why you're getting this every time. I'll create a case to have this fixed.

    For now, if this dialog appears and you know it didn't crash, you can simply "Cancel"

  • Dave Hooton
    Dave Hooton MVP Posts: 35,683

    That ".hang" file is detected and reported to our crash server which explains why you're getting this every time. I'll create a case to have this fixed.

    But it took yet another reminder to get around to this!?

    Dave
    ===

    Windows 11 & Android 13

  • Jack Caviness
    Jack Caviness MVP Posts: 13,491

    That ".hang" file is detected and reported to our crash server which explains why you're getting this every time. I'll create a case to have this fixed.

    But it took yet another reminder to get around to this!?

    I could be wrong, but this seems to be a different cause. Believe previously, these irritating requests were caused by the presence of a crash report in the logging folder.

  • LimJK
    LimJK Member Posts: 1,068

    Jack,

    my work around, not sure it will work for you. 

    • Start logos 5
    • remove all log files
    • quit logos. I waited to make sure it quits
    • start logos again

    all the best

    JK

    MacBookPro Retina 15" Late 2013 2.6GHz RAM:16GB SSD:500GB macOS Sierra 10.12.3 | iPhone 7 Plus iOS 10.2.1

  • Angela Murashov
    Angela Murashov Member Posts: 1,532

    I'll create a case to have this fixed.

    This should be fixed in 5.2a SR-4. 

  • Jack Caviness
    Jack Caviness MVP Posts: 13,491

    I'll create a case to have this fixed.

    This should be fixed in 5.2a SR-4. 

    And it appears that it is indeed fixed [<:o)]. Thank you Logos