Safari crashes as I type certain queries in the Address Bar

At this point I recommend concentrating on solutions likely to advance troubleshooting. For example, try a different Search Engine, since Safari's "Smart Search Field" populates data from your chosen Search Engine, among other sources. Google for example uploads every single keystroke you type in real time, which — aside from being the very definition of a keylogger — has been known to cause problems.

The "Similar questions" linked in one or more of those related reports will offer similar solutions. For example, Safari 16.5.2 crashes when I enter 'san' in the address field - Apple Community contains additional relevant Discussions, with links to yet even more. Some of them are old, some of them are new, a few of them identified a definitive solution, but many did not.

If you run across a solution that works for you, please let us know what it may be. If you exhaust every one, the only solution is to contact Apple and tell them about it: Official Apple Support, but even that may not lead to a solution. It's been going on for years.

Update macOS, but this has been an ongoing problem for years.

macOS 26.6.1 is the current release, as of yesterday.

Recent, related reports with proposed solutions that may help:

Safari closes unexpectedly - Apple Community

Safari crashes every time I try to type Herroom in the search bar - Apple Community

typing 'verizon.com' in search field crashes Safari - Apple Community

Were you able to advance troubleshooting? If you contacted Apple and they couldn't help, even that would be another data point.

This annoying problem shouldn't be happening after all these years. Safari should never crash.

For about the past year, Safari on Sonoma has crashed every time I try to autofill a credit card number. Now, the latest "update" has introduced two more crashers (this one and one other) that are burning me on a near-daily basis with no workaround.

Did nobody run the static analyzer before they released this version of Safari? Because clang's static analyzer should have caught this. The whole reason Apple built clang in the first place was to prevent bugs like this.

How did software with such severe bugs get released? Apple used to be better than this. Are they relying too much on vibe coding and not enough on actual engineering best practices, like writing tests, fixing compiler warnings, and having people test the software before it goes out the door? What's going on?

Safari used to be by far the best, most reliable, most lightweight browser out there. But now, the user experience has degraded so much, so quickly, that I'm on the verge of removing it from my Dock entirely and porting all of my credentials to another browser.

I thought we got past problems of the browser constantly crashing when we moved away from Mac OS 9. At least it isn't crashing the whole OS. Yet.

Apple needs to get back to "It just works." Because the second that stops being true — the second the experience starts to degrade because of constant crashes that never gets fixed — you start to lose customers, and before long, you're beleaguered all over again. It's time to right the ship before it's too late. Whatever changed in the last couple of years at Apple, please stop doing that.

Just saying.