3 ms·

Crashing not just the tab but freezing the whole browse and desktop UI on a non malicious well formed standard compatible pice of wasm... That (freezing the wh

Crashing not just the tab but freezing the whole browse and desktop UI on a non malicious well formed standard compatible pice of wasm... That (freezing the whole desktop) shouldn't even be possible even if safari has some bug. also no usable crash report or anything, no way to debug it etc. Sure that's just one maybe especially unlucky example. And my comment comes from a "additional cost safari imposes compared to e.g Firefox" point of view. So I'm counting long outstanding missing features as bug (except if missing for reasonable privacy concerns). Anyway as far as I can tell it's not as bad as IE in it's later days, but not that much better (wrt. cost it forces onto you).

acdha 5y ago
That sounds like you may have an issue with the total amount of RAM used until it eventually failed but that's an edge case, not “a buggy mess”, and it's not like neither Chrome nor Firefox never crash. It's been at least half a decade since one of them has been notably more or less reliable than the others in my experience. Regarding crash logs, Safari uses the same system crash reporter as everything else. If you want to see those, look in the Console app or use “defaults write com.apple.CrashReporter DialogType prompt” or the Crash Reporter Prefs tool from the Additional Tools for Xcode package to make crashes trigger a prompt. > And my comment comes from a "additional cost safari imposes compared to e.g Firefox" point of view. Welcome to web development? Preferring one browser always means that you perceive other browsers as a cost because inevitably you will run into a bug or compatibility issue in the one(s) you test less frequently with. It's less common in all browsers these days but it's still pretty much a given that I'll find something unexpected in one of the 3 browsers I end up supporting.

acdha 5y ago

That sounds like you may have an issue with the total amount of RAM used until it eventually failed but that's an edge case, not “a buggy mess”, and it's not like neither Chrome nor Firefox never crash. It's been at least half a decade since one of them has been notably more or less reliable than the others in my experience. Regarding crash logs, Safari uses the same system crash reporter as everything else. If you want to see those, look in the Console app or use “defaults write com.apple.CrashReporter DialogType prompt” or the Crash Reporter Prefs tool from the Additional Tools for Xcode package to make crashes trigger a prompt. > And my comment comes from a "additional cost safari imposes compared to e.g Firefox" point of view. Welcome to web development? Preferring one browser always means that you perceive other browsers as a cost because inevitably you will run into a bug or compatibility issue in the one(s) you test less frequently with. It's less common in all browsers these days but it's still pretty much a given that I'll find something unexpected in one of the 3 browsers I end up supporting.