BUG: "Logos quit unexpectedly" -- except it didn't

fgh
fgh Member Posts: 8,948 ✭✭✭
edited November 20 in English Forum

As I said at http://community.logos.com/forums/p/82138/583394.aspx#583394 I'm still seeing crashes and warning messages that were supposed to be fixed.

Here's an example of the latter. I did a perfectly normal 'Quit' of the program -- no sign that it was crashing -- but the next time I open I get a "Logos quit unexpectedly" message.

Logs: 4621.LogosLogs.20140414-135508.zip

Mac Pro (late 2013) OS 12.6.2

Comments

  • Tom Philpot (Faithlife)
    Tom Philpot (Faithlife) Member, Logos Employee Posts: 1,913

    It looks like the "crash" log that was sent was an old one from 4-6-2014 when you were running 5.2a (5.2.1.0067).

    Would you mind running the following command from Terminal and pasting the output here? (You'll need to make sure it's all on one line)

    defaults read com.logos.Logos "CrashReportSender.lastCrashDate" && ls -lt ~/Library/Logs/DiagnosticReports/Logos_*.crash | head -n5

    Mobile Development Team Lead

  • fgh
    fgh Member Posts: 8,948 ✭✭✭

    It looks like the "crash" log that was sent was an old one from 4-6-2014 when you were running 5.2a (5.2.1.0067).

    The last Logos crash report Apple created in DiagnosticReports is from that date. As you could see, the last in the Logos Logging folder is from yesterday, but 0 K (I'm pretty certain I didn't have any crash yesterday). None from today, when this 'unexpected quit' is supposed to have taken place.

    Would you mind running the following command from Terminal and pasting the output here?

    2014-04-13 21:38:25 +0200
    -rw-------@ 1 XX staff 99108 13 Apr 21:38 /Users/XX/Library/Logs/DiagnosticReports/Logos_2014-04-06-234152_XXs-Mac-mini.crash
    -rw-------@ 1 XX staff 111768 6 Apr 20:41 /Users/XX/Library/Logs/DiagnosticReports/Logos_2014-04-01-122259_XXs-Mac-mini.crash
    c193-14-20-23:~ XX$     (With a few letters changed to X's.) 

    Looks like that probably says the same as I just said above.[:)]

    Mac Pro (late 2013) OS 12.6.2

  • Tom Philpot (Faithlife)
    Tom Philpot (Faithlife) Member, Logos Employee Posts: 1,913

    The problem is that the latest crash report file (Logos_2014-04-06-234152_XXs-Mac-mini.crash) was modifed on Apr 13 at 9:38 PM, which was after it was originally submitted. Currently, if a crash report is modified it will get resubmitted because the crash reporter looks for a more recently modified crash report than the last time it sent a report. 

    I'll file a bug to look into checking for the creation time, rather than the modification time.

    Mobile Development Team Lead

  • fgh
    fgh Member Posts: 8,948 ✭✭✭

    The problem is that the latest crash report file (Logos_2014-04-06-234152_XXs-Mac-mini.crash) was modifed on Apr 13 at 9:38 PM, which was after it was originally submitted.

    I tried to take a stroll down memory lane (a k a Time Machine) to see if it had always been the case that Apple's crash reports got 'modified' by later crashes. Turns out that the entire Logs folder is missing from Time Machine. And I haven't excluded it. Surely that isn't as it should be?

    I'll file a bug to look into checking for the creation time, rather than the modification time.

    Thanks.

    I also had a hang/force quit shortly after my last post, but I've kind of given up about you ever fixing those for me.

    Mac Pro (late 2013) OS 12.6.2

  • Alan Macgregor
    Alan Macgregor Member Posts: 2,438 ✭✭✭

    Tom

    Have a look at this resurrected thread. The "old man" is back. The zombie bug returns from the grave? Whatever. Personally, I think of it as an extra splash screen, designed to annoy both users and developers in equal measure.

    Every blessing

    Alan

    iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8

    MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8

    iPad Pro 32GB WiFi iOS 13.5.1

    iPhone 8+ 64GB iOS 13.5.1

  • Jack Caviness
    Jack Caviness MVP Posts: 13,514

    Personally, I think of it as an extra splash screen, designed to annoy both users and developers in equal measure.

    Does not seem to have annoyed developers as much as it does us users [8-|]

  • Tom Philpot (Faithlife)
    Tom Philpot (Faithlife) Member, Logos Employee Posts: 1,913

    Personally, I think of it as an extra splash screen, designed to annoy both users and developers in equal measure.

    Does not seem to have annoyed developers as much as it does us users Geeked

    Jack,

    The developers occasionally introduce crashes and fix them in the normal course of development, so in Debug builds (as opposed to Release builds that we ship to end users) the crash reporting dialog is disabled. Plus, we don't want to fill up our crash reports database with spurious, one-off errors that only one developer experienced working on his machine. So, hopefully that provides an explanation as to why we didn't notice this sooner.

    But, believe me, bugs in our app do bug those of us who work on this app. It's a matter of personal and professional pride.

    This should be fixed in SR-4.

    Mobile Development Team Lead

  • Tom Philpot (Faithlife)
    Tom Philpot (Faithlife) Member, Logos Employee Posts: 1,913

    Alan,

    Thanks for the grace and sense of humour! And thanks for taking the time to report it. Again, sorry for the inconvenience.

    Tom

    Mobile Development Team Lead

  • Jack Caviness
    Jack Caviness MVP Posts: 13,514

    But, believe me, bugs in our app do bug those of us who work on this app. It's a matter of personal and professional pride.

    I did add a smile to my comment. [:D]

  • Tom Philpot (Faithlife)
    Tom Philpot (Faithlife) Member, Logos Employee Posts: 1,913

    Mobile Development Team Lead

  • Michael A. Lasley
    Michael A. Lasley Member Posts: 226

    It's happening again! 5.2a SR-4 (5.2.1.0131) MAC

  • Alan Macgregor
    Alan Macgregor Member Posts: 2,438 ✭✭✭

    It was fixed in SR-5. Now it's back again in SR-6. [:'(] This is a real Romans 7 "old man"! It just doesn't want to die. This isn't just a bug; it's a cockroach! Must be Wall-E's pal. [;)]

    Every blessing

    Alan

    iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8

    MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8

    iPad Pro 32GB WiFi iOS 13.5.1

    iPhone 8+ 64GB iOS 13.5.1

  • Tom Philpot (Faithlife)
    Tom Philpot (Faithlife) Member, Logos Employee Posts: 1,913

    Alan,

    It looks like that crash log that was submitted was dated:

    Date/Time: 2014-03-26 08:31:22 +0000

    Do you have a crash report in /Library/Logs/ or ~/Library/Logs with "Logos_2014-03-26" in the name? If so, what's the full name of the file?

    Mobile Development Team Lead

  • Alan Macgregor
    Alan Macgregor Member Posts: 2,438 ✭✭✭

    Tom

    Sorry, I'm not at my office desktop today but I'll be back tomorrow. I'll try to dig it out then. Puzzled about the date though. I posted the new log report just the other day.

    Every blessing

    Alan

    iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8

    MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8

    iPad Pro 32GB WiFi iOS 13.5.1

    iPhone 8+ 64GB iOS 13.5.1