Safari Version 14.0.1 Unexpectedly Quits

Bradley Wagner wrote:

ddkilzer wrote:

The `Namespace ASSERTIOND, Code 0xd00d2bad` crash is fixed in Safari that ships with macOS Big Sur 11.2. Please update when you're able to do so.

11.2 is out? Not seeing it available

//:0

https://discussions.apple.com/content/attachment/3094cfc6-6f6c-48ae-aa99-e9574956f7f6

Yes, you are correct. It is fixed in the latest macOS 11.2 s-e-e-d, but you may want to wait for the official release to update.

https://en.wikipedia.org/wiki/MacOS_Big_Sur#Release_history

I’ve removed all extensions and it stopped crashing... so far added back 1Password and Better with no issues....

The `Namespace ASSERTIOND, Code 0xd00d2bad` crash is fixed in Safari that ships with macOS Big Sur 11.2. Please update when you're able to do so.

ddkilzer wrote:

The `Namespace ASSERTIOND, Code 0xd00d2bad` crash is fixed in Safari that ships with macOS Big Sur 11.2. Please update when you're able to do so.

11.2 is out? Not seeing it available

Switching to Safari Technology Preview also solved the problem for me. The standard Safari 14.0.2 would crash between one and three times a day. I've been using Technology Preview 14.1 extensively for over a week with no crashes.

Finally 11.2 went public and it seems to have solved the issue. Although apple does not mention it in the notes at all.

Yep, confirmed that 11.2 seems to have fixed it. Haven't it crash since upgrading.

See the main thread on this debacle: https://discussions.apple.com/thread/252051818

Best report it via feedback - links in that thread for user feedback and developer feedback.

I guess I solved the problem of Safari crashing every day by installing Safari Technology Preview. It's been working for a few days now with no issues.

Safari 14.0.1 on Mojave also crashes on certain sites. I reinstalled Mojave which yields v12.0 with no issues, I upgraded via the supplemental update to 14.0 with no issues, but installing the offered Safari update installs 14.0.1 which crashes again.

MacOS Big Sur 11.1 was released today. I upgraded immediately, and to my surprise Safari is not closing itself since the update. I wonder, is the issue fixed altogether despite the fact that Apple does't mention it at all, or is it temporary, will it come back again. I'm not sure.

I was just thinking the exact same thing. I am going to try it now and report back. Ever since I downloaded Big Sur or should I possibly say Big Turd my safari unexpectedly quits numerous times a day especially after my system goes to sleep. When "trying" to read and understand the error codes I am getting the thing I keep noticing is all the extensions name are listed so I am wondering if it is not so much just the update as it is the extensions in conjunction with the updated software. Error code below. Corpse...that doesn't sound good..lol

Exception Type: EXC_CRASH (SIGKILL)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace ASSERTIOND, Code 0xd00d2bad

Mine is crashing daily, overnight, while my Mac is asleep.

I've now added back Honey and still ok..... I'll give it another 24 hours. Grammarly and Screenshot For Safari are the final 2 for me not on.....

Big Sur has caused havoc to my MacBook Air (Retina, 13-inch, 2019)

• Safari crashes when I go to a specific website (like United Airlines & others)
• WhatsApp for macOS crashes every time I copy/paste anything to a chat
• The Foreign Exchange app I used in widgets will no longer allow me to input any amount without opening in a new window.
• I can no longer see "battery %". I have to open the battery page under System Preferences to get the simple update on what % of the battery is left.

Is this an upgrade? Or a giant leap into a series of crashes?