HearthSim / HSTracker

A deck tracker and deck manager for Hearthstone on macOS
https://hsreplay.net/downloads/
MIT License
1.19k stars 177 forks source link

2.5.5 crashes at launch. #1324

Closed HiddenJester closed 1 year ago

HiddenJester commented 1 year ago

Describe the bug Release 2.5.5 reliably crashes as startup.

To Reproduce Steps to reproduce the behavior:

  1. Install 2.5.5.
  2. Launch it
  3. It'll crash, the Apple crash reporter comes up.
  4. Launch it again
  5. The HSTracker crash reporter dialog will come up. Then the app will crash again.

Game mode This is all happening before I launch Heartsthone. Simply running HSTracker is sufficient.

Expected behavior HSTracker should be running.

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

Version (please complete the following information): 2.5.5. Rolling back to 2.5.4 launches without issue. I re-downloaded 2.5.5 and reinstalled it a second time and confirmed the same behavior.

Additional context I did send several "anonymous crash reports" when HSTracker prompted me on a subsequent launch.

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

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

dkavner commented 1 year ago

Same issue. I got an error that it couldn't find the crash report and so it dumped this to a terminal window:

================================================================= Native Crash Reporting

Got a UNKNOWN while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application.

================================================================= Native stacktrace:

0x1021d5d94 - /Applications/HSTracker.app/Contents/Frameworks/libcoreclr.dylib : mono_dump_native_crash_info
0x102179fce - /Applications/HSTracker.app/Contents/Frameworks/libcoreclr.dylib : mono_handle_native_crash
0x1020d05ae - /Applications/HSTracker.app/Contents/Frameworks/libcoreclr.dylib : mono_crashing_signal_handler
0x7fff20802d7d - /usr/lib/system/libsystem_platform.dylib : _sigtramp
0x100000000 - Unknown
0x10124c7c6 - /Applications/HSTracker.app/Contents/MacOS/HSTracker : 
0x1012913bd - /Applications/HSTracker.app/Contents/MacOS/HSTracker : 
0x101154be9 - /Applications/HSTracker.app/Contents/MacOS/HSTracker : 
0x7fff20612623 - /usr/lib/system/libdispatch.dylib : _dispatch_call_block_and_release
0x7fff20613806 - /usr/lib/system/libdispatch.dylib : _dispatch_client_callout
0x7fff20615e37 - /usr/lib/system/libdispatch.dylib : _dispatch_queue_override_invoke
0x7fff20622818 - /usr/lib/system/libdispatch.dylib : _dispatch_root_queue_drain
0x7fff20622f70 - /usr/lib/system/libdispatch.dylib : _dispatch_worker_thread2
0x7fff207ba417 - /usr/lib/system/libsystem_pthread.dylib : _pthread_wqthread
0x7fff207b942f - /usr/lib/system/libsystem_pthread.dylib : start_wqthread

================================================================= External Debugger Dump:

================================================================= Basic Fault Address Reporting

Memory around native instruction pointer (0x7fff2cba4367):0x7fff2cba4357 e5 b9 2c 00 48 8b 65 d0 4c 89 ff e8 99 65 32 00 ..,.H.e.L....e2. 0x7fff2cba4367 0f 0b 0f 1f 80 00 00 00 00 55 48 89 e5 31 c0 5d .........UH..1.] 0x7fff2cba4377 c3 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 57 41 .........UH..AWA 0x7fff2cba4387 56 41 55 41 54 53 50 4d 89 cc 45 89 c6 49 89 cf VAUATSPM..E..I..

================================================================= Managed Stacktrace:

================================================================= Abort logout

iblackscreen commented 1 year ago

Hey there, Same for me. I am on the m1 (arm) chip. This could maybe be part of the problem? If you need anything, more reports, specifics, let me/us know.

TyphoonFL commented 1 year ago

Same for me, also on M1 chip

dkavner commented 1 year ago

I'm on Intel, so the issue isn't due to the type of chip.

fmoraes74 commented 1 year ago

Fix incoming with 2.5.6. The build picked up a new version of BobsBuddy which broke the code. I wasn't expecting it and didn't test it before releasing, so my bad.

fmoraes74 commented 1 year ago

Please try the newly released 2.5.6

iblackscreen commented 1 year ago

Fixed. Thanks