Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Anyone else seeing frequent Safari crashes? Or use LastPass, AdBlock Plus, Grammarly?

F

Fomalhaut

macrumors 68020
Original poster
Oct 6, 2020
2,022
1,747
Since getting my M1 Mac Mini, I've had about half a dozen crashes of Safari, where it just closes all windows instantly, without any hint of problems previously.

It doesn't seem to be related to any particular web pages, but seems to happen when I am trying to open a new web page, on an existing tab. I have about 50-60 browser tabs open, but memory usage is not particularly high (low green memory pressure).

I am running 3 Safari plug-ins: LastPass, Adblock Plus and Grammarly.

Not much information that I can see from the crash report:


Process: Safari [394]
Path: /Applications/Safari.app/Contents/MacOS/Safari
Identifier: com.apple.Safari
Version: 14.0.1 (16610.2.11.51.8)
Build Info: WebBrowser-7610002011051008~1
Code Type: ARM-64 (Native)
Parent Process: ??? [1]
Responsible: Safari [394]
User ID: 501

Date/Time: 2020-12-15 16:13:50.878 +1100
OS Version: macOS 11.0.1 (20B29)
Report Version: 12
Anonymous UUID: FDBE4A9B-7409-29BF-DD4A-F4D89F1B592D

Sleep/Wake UUID: E1BFD15D-1715-41F4-8C04-CFF110B40609

Time Awake Since Boot: 73000 seconds
Time Since Wake: 27000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace ASSERTIOND, Code 0xd00d2bad

Application Specific Information:
Enabled App Extensions:
com.lastpass.lastpassmacdesktop.safariext (N24REP3BMN) (Version: 1121 - Display Version: 4.60.0) LastPass
com.grammarly.safari.extension.ext (W8F64X92K3) (Version: 16.0.163348 - Display Version: 9.22) Grammarly for Safari
org.adblockplus.adblockplussafarimac.AdblockPlusSafariToolbar (GRYYZR985A) (Version: 202011101359 - Display Version: 2.1.6) ABP Control Panel


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x000000018cd87ce8 mach_msg_trap + 8
1 libsystem_kernel.dylib 0x000000018cd88098 mach_msg + 76
2 com.apple.CoreFoundation 0x000000018cebbe88 __CFRunLoopServiceMachPort + 380
3 com.apple.CoreFoundation 0x000000018ceba35c __CFRunLoopRun + 1216
4 com.apple.CoreFoundation 0x000000018ceb9730 CFRunLoopRunSpecific + 600
5 com.apple.HIToolbox 0x00000001949c2f0c RunCurrentEventLoopInMode + 292
6 com.apple.HIToolbox 0x00000001949c2d3c ReceiveNextEventCommon + 688
7 com.apple.HIToolbox 0x00000001949c2a6c _BlockUntilNextEventMatchingListInModeWithFilter + 76
8 com.apple.AppKit 0x000000018f68edb0 _DPSNextEvent + 868
9 com.apple.AppKit 0x000000018f68d730 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1312
10 com.apple.Safari.framework 0x00000001aebc0cb4 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 236
11 com.apple.AppKit 0x000000018f67f58c -[NSApplication run] + 600
12 com.apple.AppKit 0x000000018f650d74 NSApplicationMain + 1064
13 com.apple.Safari.framework 0x00000001aeba7794 SafariMain + 456
14 libdyld.dylib 0x000000018cddcf54 start + 4
--------

Any ideas what might be causing the crashes?
 
  • Like
Reactions: skment
I would uninstall the extensions and then re-add them one at a time to find out which one is causing the problem. Then you can report it to the developer. I've been using Safari every day on my M1 MacBook Air and haven't had a single crash. So what you are seeing is not normal. I don't use any of those extensions so I can't help with tracking down which one is causing the trouble.

Edit: And you should update to macOS 11.1.
 
jdb8167 said:
I would uninstall the extensions and then re-add them one at a time to find out which one is causing the problem. Then you can report it to the developer. I've been using Safari every day on my M1 MacBook Air and haven't had a single crash. So what you are seeing is not normal. I don't use any of those extensions so I can't help with tracking down which one is causing the trouble.

Edit: And you should update to macOS 11.1.
Click to expand...
Thanks for that. This is pretty much what I was planning to do. I can live without the plug-ins (although LastPass is useful, but has its own stand-alone app).

I'm always cautious with installing new updates immediately unless there's a serious security hole, but it's been a few days and 11.1 seems to be stable, so I'll try that first.
 
acidfast7_redux said:
I always thought Grammarly was a spammy scam.

Also, this is the first place, I have ever seen it, MacRumors, but why do people have 50+ borrower tabs open?
Click to expand...
Ah, the old "why do you have so many tabs open?" question. We discussed this at length here: https://forums.macrumors.com/thread...my-needs.2273883/?post=29360940#post-29360940

To summarize, I need to monitor cloud platforms that have a lot a console windows (6-12 tabs), have reference documentation open for my current tasks (c. 5-10 tabs), research blogs / docs for multiple topics to support software development tasks, project documentation pages being read or worked on (wikis, Google docs, web-mail accounts) - at least 5 tabs normally. Application tabs for testing my work. Task boards (Jira, Asana, Miro etc.). And Macrumors.com of course :)

I have to work on a dozen different tasks a day, so it's more efficient to have pages that refer to my day's work left open, rather than closing, searching bookmarks, open pages, scrolling to the relevant information, and re-opening every time I switch focus (dozens of times a day). I do try to tidy them up at the end of the day, but sometimes they add up during the week!
 
I doubt the extensions are at fault as it doesn't look like we have any in common. I have also disabled everything but my own I develop and still encounter the crashes. I have been been encountering them since updating from 11.0.1 to 11.1 in Safari 14 (and iMessage among others) several times a day and it seems fairly common:
www.google.com

ð big sur safari Namespace ASSERTIOND, Code 0xd00d2bad - Google Search

www.google.com

The vast majority of the times it seems to be occurring while the display is asleep or the system is locked or sleeping.
 
I have the M1 Mini and have not had Safari crash once since switching. I also use Grammarly so I doubt that is the issue. Best bet is what you are already planning, update to 11.1, and install the extensions one by one.
 
I have the same problem with Big Sur crashing with the same Termination Reason but mine is a 2017 iMac so not M1. The only two extensions I have installed are 1Password and Downie.
 
I'm getting the same error - m1 Mac mini on Big Sur 11.1. Every morning I come back to my machine and safari's crashed. Maybe something to do with an external monitor?

I've got 1Password and 1Blocker as extensions.
 
kashirat said:
I'm getting the same error - m1 Mac mini on Big Sur 11.1. Every morning I come back to my machine and safari's crashed. Maybe something to do with an external monitor?

I've got 1Password and 1Blocker as extensions.
Click to expand...
I use 1Blocker. No crashes at all.
 
I kept having crashes across safari and adobe products. Ended up returning the machine and bought a new one hoping it was a lemon but the new one did the same as well.

everyone on here responded to my thread saying it was user error. But I've been a Mac user for 10+ years and have owned 3 different MacBook models over the years.

I'm not convinced it was something I was doing but can not figure out what happened.
 
kougra6541 said:
I kept having crashes across safari and adobe products. Ended up returning the machine and bought a new one hoping it was a lemon but the new one did the same as well.

everyone on here responded to my thread saying it was user error. But I've been a Mac user for 10+ years and have owned 3 different MacBook models over the years.

I'm not convinced it was something I was doing but can not figure out what happened.
Click to expand...
I don't use Adobe products but I can tell you that if your M1 Mac is working normally, Safari doesn't crash. It's wrong to call it user error. No matter what, software shouldn't crash without at least reporting what the problem is. If it is an extension, Apple should fix Safari so that what ever error the extension is causing is at least reported to the user.

Edit: Also there should be crash reports that might not mean much to the user but if supplied to Apple or the developer, can pinpoint where the problem is.
 
It's NOTHING to do with the M1.

My 2017 Intel iMac started doing this after installing Bug Sur.
 
kougra6541 said:
I kept having crashes across safari and adobe products. Ended up returning the machine and bought a new one hoping it was a lemon but the new one did the same as well.

everyone on here responded to my thread saying it was user error. But I've been a Mac user for 10+ years and have owned 3 different MacBook models over the years.

I'm not convinced it was something I was doing but can not figure out what happened.
Click to expand...

Well, I would say if it happened on two different systems, then the most likely culprit would seem to be pointing towards software. Unless there was an inherent issue with the M1, and the lack of a product recall would suggest there isn’t. That and if it were something inherent to the hardware, it would be unavoidable, we would all be seeing the same issues.

Did you experience crashes in Safari when the system was setup anew, for instance, before installing any other software, or plugins if you used any? Did you ultimately find a solution?

I’m not doubting that you had problems, wouldn’t dare suggest that you didn’t experience issues, I’ve experienced my share of bizarre head-scratchers over the years. I’m just always curious as to the why.

There’s so many variables in these things, although we are all using the same basic hardware and software to begin with. The addition of different software and indeed hardware, can throw up such unexpected results that I find it can be beneficial to others to share experiences.
 
Yep, just adding myself on the list with MBP 16" using LastPass and AdGuard as the only plugins. Have any of you found a solution? Nowadays (that is anytime after like 2010), it feel really out of place to have browser crashing that often...
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back