Constant crashes

[Flyslinger2]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Game mode

• [ ] Standard

• [ ] Wild

• [ ] Classic

• [ ] Arena

• [ ] Battlegrounds

• [ ] Duels

• [ ] Mercenaries

• [ ] Tavern Brawl

• [ ] Dungeon Run/Book of Heroes/Book of Mercenaries

• [ ] Single Player

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Version (please complete the following information): Important: please specify the version of HSTracker that you are using

Additional context Add any other context about the problem here.

Log file Attach the hstracker.log file found under /Users/<userid>/Library/Logs/HSTracker/ directory (or use the Help->Open log directory)

Deck code If the problem happens with a specific deck, please include the deck code used.

[fmoraes74]

Unfortunately a screenshot is not sufficient for debugging crashes. Have you updated your MacOS to a newer version?

[Flyslinger2]

Current

Mark R. Sigsbee, CISSP

SUNet PKI Support Team @.**@.> (301)509-7592 (cell)

[cid:b26fca5b-ca01-4a1c-b81a-e7af1ffe6e7b]

---

From: Francisco Moraes @.> Sent: Wednesday, June 28, 2023 12:04 PM To: HearthSim/HSTracker @.> Cc: Mark Sigsbee @.>; Author @.> Subject: Re: [HearthSim/HSTracker] Constant crashes (Issue #1316)

Unfortunately a screenshot is not sufficient for debugging crashes. Have you updated your MacOS to a newer version?

— Reply to this email directly, view it on GitHubhttps://github.com/HearthSim/HSTracker/issues/1316#issuecomment-1611705524, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJHY7I6GGCDWKWLOY4U2JLDXNRIYPANCNFSM6AAAAAAZVXA4AA. You are receiving this because you authored the thread.Message ID: @.***>

[fmoraes74]

Current MacOS is 13.4.1.

You can attach a crash report found in the Console application and I can take a look but I cannot make any promises as there is nothing similar being reported by others.

[alsospacebar]

I'm seeing crashes with Bassgill comps. I'm attaching hstracker.log and a crash log from my last game where it just happened (note I am on the latest Ventura Beta).

hstracker.log HSTracker-2023-08-20-120110.json.txt

[fmoraes74]

Seems like some went off in the BobsBuddy integration or Mono. I will try to update the CoreCLR to the latest version for the next patch and see if that helps. These crashes are tricky and I will try to find some solution but it is not trivial.

[alsospacebar]

I'm aware this probably isn't the right place but I just want to express my appreciation for you having a new version so fast with this massively complex patch. Very impressed and thankful.

[fmoraes74]

I'm aware this probably isn't the right place but I just want to express my appreciation for you having a new version so fast with this massively complex patch. Very impressed and thankful.

Thanks for the kind words. I hope the new version may have helped with the crashes but no guarantees at this point

[alsospacebar]

I've not seen any more Bassgill crashes so far (although it didn't happen always, just most of the time). I did see a crash on startup - hstracker was the first app I started after a reboot. I've only seen this once, ever, so it may not matter. Logs attached. hstracker.log startup-crash.txt

(do you prefer these text dumps or the .ips files from DiagnosticReports?)

[alsospacebar]

Today another crash - I think this is Rylak related, but am not sure. hstracker.log tracker-crash.txt

[fmoraes74]

Does this still happen with version 2.5.4?

[alsospacebar]

I have another Rylak crash - apologies, I don't have a hstracker.log . crash.txt

[alsospacebar]

Does this still happen with version 2.5.4?

Here's a startup crash with 2.5.7, after a reboot.

hstracker.log startup-crash.txt

[fmoraes74]

I am able to recreate the crash on a standalone attempt, hope to have fix by next version.

[Flyslinger2]

OK!

[fmoraes74]

This is fixed in version 2.5.8. Please reopen if that's not the case.