Native access quit unexpectedly6/7/2023 Thanks a lot for quick support, however, the latest beta version v2.9.11 will still crash on 10.15.7Īttach the details, contact me if need more info Crash Details on 2.9.11-beta1 With so much effort you've all put into fixing an upstream issue, and only for a small fraction of your users - reproducing the crash on platforms going two or three major versions back - I can only say: Thank you! Thank you for not throwing some of your power users (not willing to use the current, more consumer-oriented platforms) overboard. I personally voluntarily choose to run tried and tested and simply stable versions as 10.13, 10.14 (or 10.15 if inevitable) compared to current generations, so I usually have to rely on older app releases, service/support EOLs and degraded support and functionality overall. I too encountered this issue straight away yet dismissed it given the age and uptime of the device and its long unsupported OS version. PS: I'm amazed with the amount of work you have… how much attention to detail and care for your users you show every single day. ![]() With 2.9.11 stable out now this apparently seems fixed, thanks! (10.14.6 Mojave) Termination Reason: Namespace SIGNAL, Code 0xb Termination Signal: Segmentation fault: 11 Path: /Applications/GitHub Desktop.app/Contents/MacOS/GitHub DesktopĪnonymous UUID: 193B795B-28FC-40D1-1011-35DCEE165FE6Ĭrashed Thread: 0 Dispatch queue: -threadĮxception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
0 Comments
Leave a Reply. |