There must have been some automatic update, and now it's, 90 percent loaded over and over, and the infamous, safari is not responding.
Anyone else?, or am I just lucky.
I wonder if something like AdGuard Pro and Hyperweb would actually be useful for an issue like this. Do people have worthwhile ad blockers running? Has that had any impact on if this bug appears or not? My reasoning is based on the idea that blocking ads, making sure the cookies are accepted, etc. could make the website less resource intensive
I use Duck Duck Go VPN and Wipr for Safari, and I still get it. Granted I am on an old intel MBP running Ventura (13.6.4) and Safari 17.3, for what its worth.
Running the latest Sonoma update on an MBP with M2Pro - a couple of updates ago I also installed Wipr, I wasn't getting the not responding prompt all that much and not sure what improved for me, the updates or Wipr but pages do seem to load faster for me, at least that is my perception.
I'm seeing SNR with a strange new twist. I go to a website or follow a link. Then crickets. Rather than hearing the proclamation, Safari Not Responding, I get silence. VoiceOver doesn't announce the page title, nor the first element, nor does it make the undocumented happy noice that I've come to associate with a successful page load. Sometimes, trying to interact with the website wakes it up. Sometimes not.
When this happens, I Command+Tab away to another app, like Mail, and VoiceOver announces, Mail. Then I Command+Tab back, and I hear VoiceOver announce, Safari, then very quickly, Mail. As if it has switched back to the other app all by itself.
I will do my best to ignore suggestions and ideas with no tangible evidence of benefit, including but not limited to ad blockers, updating hardware, and any speculation that busy versus lightweight sites might be the cause. No guarantees, though. These types of suggestions, along with gamma rays, have been known to turn me into The Incredible Hulk.
14.2 did seem to improve things, but the last couple of weeks - possibly since 14.3 - I've had it quite a lot. Last week for me was the worst it has ever been. I've noticed in activity monitor I've got MauiAUSP appearing quite a bit and using a chunk of CPU. Think this is the process for handling ios apps on the Mac isn't it? Not sure what app that would be. I did wonder if it was the alpha of vocr 2 as that was the only new thing I had running. I've since upgraded it to beta 2 and stopped it running on startup and I maye be getting an improvement. I've been all over the place this week so I can't be sure.
But at any rate, other apps don't have the problem so might be a red herring.
I've also had a few occasions where the Mac seems to have just totally locked up and gone quiet. Then after a minute it would suddenly go crazy as it processes all the commands it has stacked up.
I'm using a decent Macbook Pro M2 which is way over specced for what I need.
Just had a really bad one but noticed that Safari was using up almost all my CPU on this one page. No idea if it's a VO thing or not. I guess the problem is that we get the same symptom for a number of different underlying issues. Just think WebKit is perhaps not very good.
I have seen the exact behavior that Paul described while accessing a drive that is connected to an Airport Extreme that I use as a dumb switch just for the purpose of using a network drive, sometimes it'll act just as Paul described for a minute or so before I'm able to browse files on the drive. Not getting this on Safari anymore, btw I did not get the ad blocker for the SNR issue, just to stop the cookie policy notices that were driving me mad, and it absolutely works, for this alone it's worth the couple of bucks, and I do think pages load slightly faster, but I'm not trying to sell ad blocker apps, just sharing my experience.
I'm finding it more productive to use Linux as my primary operating system at the moment, even though the Mac is the newer and faster machine. The Mac is a secondary system fro me at this stage.
I can work around MacOS accessibility bugs, but with Linux, I can use the tools I want without having to deal with accessibility issues that harm my productivity so often.
I don't want to use Windows for security and reliability reasons, and because it isn't natively a UNIX-like system.
The case against Macs has never been greater. Though it does look like Apple have just fixed that VMWare crashing bug, I'm still pretty cheesed off about it.
What's your Linux environment, if you don't mind me asking? Choice of hardware? Desktop environment? Yes, I know, OT ...
Currently Arch Linux, GNOME 45, directly on x86-64 hardware.
Asahi Linux would be an option for my Apple Silicon Mac, but according to what I've heard, the audio support still isn't working - and I care about that.
I think MacOS has good braille display features, but as is the case elsewhere, the bugs are the problem, including the tendency to skip text while panning the display in some circumstances.
I don't know whether MacOS caches the accessibility API tree. Linux does, and this is responsible, apparently, for recent performance improvements. the latest Linux project, sponsored by the GNOME Foundation, is to reduce the amount of inter-process communication still further with a new accessibility architecture similar to what Chromium and Firefox implement internally. The basic idea is taht the application writes updates to the accessibility tree as they occur, instead of acting primarily upon API calls from the screen reader or other assistive technology. The assistive technology maintains a cache.
It's possible that MacOS has similar issues and that "not responding" is a symptom of performance problems that could be eliminated if Apple were to rework their accessibility architecture for greater efficiency. That's just speculation, however.
I personally have not experienced this for quite a long time, but it sure seems like Safari not responding is still a pretty big issue for many of you.
Quite honestly though, just posting here saying you have the same issue probably won't do much to get this investigated and (hopefully) fixed by Apple.
Even if an Apple engineer from the right team happened to stumble upon this topic, chances are they might be unable to reproduce the issue themselves, as they wouldn't know on which website the issue is occurring, which Mac model this is happening on, and a whole bunch of other details that might actually enable them to get this fully resolved in an update.
In order to really make a difference here and vastly improve the likelihood of a working fix, I'd strongly recommend and encourage all of you experiencing this to submit a feedback report to Apple, using the Feedback Assistant app. You do not need to be signed up to any of Apple's beta or developer programs to do this, and you also do not need to be running a beta version of the OS.
Here's how it works:
1. Open Safari.
2. type the following into the address bar and hit Return:
applefeedback://
3. Safari should now ask for permission to open Feedback Assistant, activate the Allow button.
4. A Feedback Assistant window will now open. If prompted, type in your AppleID password and hit Return.
5. Now, press CMD-N to bring up the New Feedback window. You'll be presented with several options to choose on which OS and in which area the issue is occurring, after which you'll be able to type in a title and description for your bug report.
The text you put into your report description doesn't have to be super long honestly, but try to throw in as many potentially helpful details as you can think of. For the Safari issue, include things like which website you are trying to access, what you are trying to do when the issue occurs (e.g. does it happen immediately after typing the website URL, or only after you try to interact with the site's content), and the version of macOS you're currently on.
It is also possible to attach files to these reports. A neat thing to do here could be to capture a screen recording while the issue is happening on your machine, so that the teams at Apple will be able to observe exactly what is going on on your system, in some cases this might actually greatly help in understanding the cause of a bug, and might speed up the investigation.
Once you're done, hit the Send button to submit your feedback to Apple. You'll then be given your feedback ID (starting with "FB" followed by a bunch of digits), you can freely share this ID in public, so feel free to post it here as well after submitting your reports.
To all of you impacted by this, I really hope it gets resolved real soon. Filing these problems in the form of a feedback report will hopefully help speed things up, of course there are no guarantees as to when a particular issue will get fixed, but these reports will undoubtedly give the folks at Apple a lot more useful pointers in the right direction.
Apple engineers and employees are specifically told to avoid coming on this website because they don’t want to be misled or confuse by all the differing thoughts and use case scenarios. How do I know this? I know because of I know and the information isn’t coming from nowhere.
This site is for people using voiceover and other accessibility tools. Unfortunately, many users can barely turn their devices on. And many have specific ideas and blame everything from the weather to Putan for things they mislabel as bugs Similarly, some people refuse to upgrade their software and are reporting issues for software that can be three years old. If someone comes on the site with a new app or conceptualizes a new way to improve accessibility, they are bullied and belittled I to next year. This is a quote community that argued that touch typing was a bad idea because standard typing (double tap to type) already worked.
If apple ever came here, it was years ago. I do believe they take the applevis team feedback seriously and that is very well thought out, I formative, and provides foundation to work from. But the general applevis.com commenter. I don’t think so
Apple don't seem interested in engaging with our community at all. Yes they probably don't want to implement every single thing mentioned here, but imagine if we did have someone in Apple that was actually interested in replying to topics and taking an interest. That would make all the difference.
I absolutely agree about reporting all issues. There are problems with this however. Firstly, nothing ever gets done. I usually report via the email but I tried one problem with feedback assistant and didn't get anything back. But all bugs I've reported even when the accessibility team acknowledges that they have reproduced it, it still doesn't get addressed.
They have pointed me at this site once or twice, though, so they do know about it. Which makes it worse that they won't engage.
The other problem I have with reporting bugs is that most of the time I am using my Mac to work, so I can't be submitting any logs that contain anything relating to my work. And I have so little time and energy for this sort of thing outside work. I hate it when I have to spend the only few hours of free time I get in the week messing about with bug reports.
Apple need to actually use VoiceOver on the Mac in real-world scenarios then they would understand.
Regarding users being on old software, can you blame them? I wish I had never upgraded to Sonoma. Each version of the Mac seems worse than the last one. You wouldn't want junior staff coming in here, but even if we had one more senior person engaging with us it would be so helpful. If we had any faith at all that new software would work better than the last one, then we would all be upgrading every time.
Comments
Time to report it
It isn't happening to me under MacOS 14.3, 14-inch MacBook Pro with M1 Pro.
Your best course of action is probably to run sysdiagnose (Ctrl-Option-Command-Shift-.), and send Apple the results., Yesterday, 2:02 pm
Having the issue here
I am having this with the latest MacOS and it has been reported.
what are your specs?
OP what are your specs? Intel based Mac? M1? are you running beta? This would help but I occasionally get it but i type faster then superman flies so.
It never went away
Is there anything more to say? I have a 2022 Mac Studio M1 ultra on the fastest fiber optic line available, and I still get it, using Ventura.
I wonder if AdGuard or other add blocking would help this issue
I wonder if something like AdGuard Pro and Hyperweb would actually be useful for an issue like this. Do people have worthwhile ad blockers running? Has that had any impact on if this bug appears or not? My reasoning is based on the idea that blocking ads, making sure the cookies are accepted, etc. could make the website less resource intensive
@Ash Rein
I use Duck Duck Go VPN and Wipr for Safari, and I still get it. Granted I am on an old intel MBP running Ventura (13.6.4) and Safari 17.3, for what its worth.
not happening for me
Running the latest Sonoma update on an MBP with M2Pro - a couple of updates ago I also installed Wipr, I wasn't getting the not responding prompt all that much and not sure what improved for me, the updates or Wipr but pages do seem to load faster for me, at least that is my perception.
Crickets on Ventura 13.6.3
I'm seeing SNR with a strange new twist. I go to a website or follow a link. Then crickets. Rather than hearing the proclamation, Safari Not Responding, I get silence. VoiceOver doesn't announce the page title, nor the first element, nor does it make the undocumented happy noice that I've come to associate with a successful page load. Sometimes, trying to interact with the website wakes it up. Sometimes not.
When this happens, I Command+Tab away to another app, like Mail, and VoiceOver announces, Mail. Then I Command+Tab back, and I hear VoiceOver announce, Safari, then very quickly, Mail. As if it has switched back to the other app all by itself.
I will do my best to ignore suggestions and ideas with no tangible evidence of benefit, including but not limited to ad blockers, updating hardware, and any speculation that busy versus lightweight sites might be the cause. No guarantees, though. These types of suggestions, along with gamma rays, have been known to turn me into The Incredible Hulk.
Yes it is back
14.2 did seem to improve things, but the last couple of weeks - possibly since 14.3 - I've had it quite a lot. Last week for me was the worst it has ever been. I've noticed in activity monitor I've got MauiAUSP appearing quite a bit and using a chunk of CPU. Think this is the process for handling ios apps on the Mac isn't it? Not sure what app that would be. I did wonder if it was the alpha of vocr 2 as that was the only new thing I had running. I've since upgraded it to beta 2 and stopped it running on startup and I maye be getting an improvement. I've been all over the place this week so I can't be sure.
But at any rate, other apps don't have the problem so might be a red herring.
I've also had a few occasions where the Mac seems to have just totally locked up and gone quiet. Then after a minute it would suddenly go crazy as it processes all the commands it has stacked up.
I'm using a decent Macbook Pro M2 which is way over specced for what I need.
Red herrings
Just had a really bad one but noticed that Safari was using up almost all my CPU on this one page. No idea if it's a VO thing or not. I guess the problem is that we get the same symptom for a number of different underlying issues. Just think WebKit is perhaps not very good.
finder not responding for a network attached drive
I have seen the exact behavior that Paul described while accessing a drive that is connected to an Airport Extreme that I use as a dumb switch just for the purpose of using a network drive, sometimes it'll act just as Paul described for a minute or so before I'm able to browse files on the drive. Not getting this on Safari anymore, btw I did not get the ad blocker for the SNR issue, just to stop the cookie policy notices that were driving me mad, and it absolutely works, for this alone it's worth the couple of bucks, and I do think pages load slightly faster, but I'm not trying to sell ad blocker apps, just sharing my experience.
What works best for me
I've found that SNR's can best be bypassed by turning VoiceOver off, waiting a few seconds, and then turning VoiceOver back on.
Not experiencing this bug but...
I'm finding it more productive to use Linux as my primary operating system at the moment, even though the Mac is the newer and faster machine. The Mac is a secondary system fro me at this stage.
I can work around MacOS accessibility bugs, but with Linux, I can use the tools I want without having to deal with accessibility issues that harm my productivity so often.
I don't want to use Windows for security and reliability reasons, and because it isn't natively a UNIX-like system.
Following Recent Showstoppers
The case against Macs has never been greater. Though it does look like Apple have just fixed that VMWare crashing bug, I'm still pretty cheesed off about it.
What's your Linux environment, if you don't mind me asking? Choice of hardware? Desktop environment? Yes, I know, OT ...
Linux, accessibility architecture, and "not responding"
Currently Arch Linux, GNOME 45, directly on x86-64 hardware.
Asahi Linux would be an option for my Apple Silicon Mac, but according to what I've heard, the audio support still isn't working - and I care about that.
I think MacOS has good braille display features, but as is the case elsewhere, the bugs are the problem, including the tendency to skip text while panning the display in some circumstances.
I don't know whether MacOS caches the accessibility API tree. Linux does, and this is responsible, apparently, for recent performance improvements. the latest Linux project, sponsored by the GNOME Foundation, is to reduce the amount of inter-process communication still further with a new accessibility architecture similar to what Chromium and Firefox implement internally. The basic idea is taht the application writes updates to the accessibility tree as they occur, instead of acting primarily upon API calls from the screen reader or other assistive technology. The assistive technology maintains a cache.
It's possible that MacOS has similar issues and that "not responding" is a symptom of performance problems that could be eliminated if Apple were to rework their accessibility architecture for greater efficiency. That's just speculation, however.
Please, file feedback reports with Apple
Hey all,
I personally have not experienced this for quite a long time, but it sure seems like Safari not responding is still a pretty big issue for many of you.
Quite honestly though, just posting here saying you have the same issue probably won't do much to get this investigated and (hopefully) fixed by Apple.
Even if an Apple engineer from the right team happened to stumble upon this topic, chances are they might be unable to reproduce the issue themselves, as they wouldn't know on which website the issue is occurring, which Mac model this is happening on, and a whole bunch of other details that might actually enable them to get this fully resolved in an update.
In order to really make a difference here and vastly improve the likelihood of a working fix, I'd strongly recommend and encourage all of you experiencing this to submit a feedback report to Apple, using the Feedback Assistant app. You do not need to be signed up to any of Apple's beta or developer programs to do this, and you also do not need to be running a beta version of the OS.
Here's how it works:
1. Open Safari.
2. type the following into the address bar and hit Return:
applefeedback://
3. Safari should now ask for permission to open Feedback Assistant, activate the Allow button.
4. A Feedback Assistant window will now open. If prompted, type in your AppleID password and hit Return.
5. Now, press CMD-N to bring up the New Feedback window. You'll be presented with several options to choose on which OS and in which area the issue is occurring, after which you'll be able to type in a title and description for your bug report.
The text you put into your report description doesn't have to be super long honestly, but try to throw in as many potentially helpful details as you can think of. For the Safari issue, include things like which website you are trying to access, what you are trying to do when the issue occurs (e.g. does it happen immediately after typing the website URL, or only after you try to interact with the site's content), and the version of macOS you're currently on.
It is also possible to attach files to these reports. A neat thing to do here could be to capture a screen recording while the issue is happening on your machine, so that the teams at Apple will be able to observe exactly what is going on on your system, in some cases this might actually greatly help in understanding the cause of a bug, and might speed up the investigation.
Once you're done, hit the Send button to submit your feedback to Apple. You'll then be given your feedback ID (starting with "FB" followed by a bunch of digits), you can freely share this ID in public, so feel free to post it here as well after submitting your reports.
To all of you impacted by this, I really hope it gets resolved real soon. Filing these problems in the form of a feedback report will hopefully help speed things up, of course there are no guarantees as to when a particular issue will get fixed, but these reports will undoubtedly give the folks at Apple a lot more useful pointers in the right direction.
Robin
Apple does not come here
Apple engineers and employees are specifically told to avoid coming on this website because they don’t want to be misled or confuse by all the differing thoughts and use case scenarios. How do I know this? I know because of I know and the information isn’t coming from nowhere.
This site is for people using voiceover and other accessibility tools. Unfortunately, many users can barely turn their devices on. And many have specific ideas and blame everything from the weather to Putan for things they mislabel as bugs Similarly, some people refuse to upgrade their software and are reporting issues for software that can be three years old. If someone comes on the site with a new app or conceptualizes a new way to improve accessibility, they are bullied and belittled I to next year. This is a quote community that argued that touch typing was a bad idea because standard typing (double tap to type) already worked.
If apple ever came here, it was years ago. I do believe they take the applevis team feedback seriously and that is very well thought out, I formative, and provides foundation to work from. But the general applevis.com commenter. I don’t think so
Re: Apple coming in here
Apple don't seem interested in engaging with our community at all. Yes they probably don't want to implement every single thing mentioned here, but imagine if we did have someone in Apple that was actually interested in replying to topics and taking an interest. That would make all the difference.
I absolutely agree about reporting all issues. There are problems with this however. Firstly, nothing ever gets done. I usually report via the email but I tried one problem with feedback assistant and didn't get anything back. But all bugs I've reported even when the accessibility team acknowledges that they have reproduced it, it still doesn't get addressed.
They have pointed me at this site once or twice, though, so they do know about it. Which makes it worse that they won't engage.
The other problem I have with reporting bugs is that most of the time I am using my Mac to work, so I can't be submitting any logs that contain anything relating to my work. And I have so little time and energy for this sort of thing outside work. I hate it when I have to spend the only few hours of free time I get in the week messing about with bug reports.
Apple need to actually use VoiceOver on the Mac in real-world scenarios then they would understand.
Regarding users being on old software, can you blame them? I wish I had never upgraded to Sonoma. Each version of the Mac seems worse than the last one. You wouldn't want junior staff coming in here, but even if we had one more senior person engaging with us it would be so helpful. If we had any faith at all that new software would work better than the last one, then we would all be upgrading every time.