3 ms·
I've had at least one instance of Ghostty running on both my work and personal machine continuously since I first got access to the beta last November, and I ha
by dpatterbee 1y ago
I've had at least one instance of Ghostty running on both my work and personal machine continuously since I first got access to the beta last November, and I haven't seen a single segfault in that entire time. When have you seen them?
- mr90210 1y agoGoogle: "wikipedia Evidence of absence" Also, https://github.com/ghostty-org/ghostty/issues?q=segfault https://github.com/ghostty-org/ghostty/issues?q=segfault
- dpatterbee 1y agoSo Ghostty was first publicly released on I think December 27th last year, then 1.0.1, 1.1.0, 1.1.1, and 1.1.2 were released within the next month and a half to fix bugs found by the large influx of users, and there hasn't been a segfault reported since. I would recommend that users who are finding a large number of segfaults should probably report it to the maintainers.
- metaltyphoon 1y agoLook at the issue tracker and its history too.
- dmit 1y agoI've seen the amount of effort Mitchell &co put into ensuring memory safety of Ghostty in the 1.2 release notes, but after upgrading I am still afraid to open a new pane while there's streaming output in the current one because in 1.1.3 that meant a crash more often than not.