Screen freezes for a few seconds

It's not. The freeze happens even when the processor and memory are being used at extremely low levels and my fan is off. My laptop's up on a raised, ventilated metal platform and I type on it with a peripheral keyboard, so it's about as well ventilated as it could be. It's a periodic kernel panic from some kind of glitch in the graphics. If you scroll through this thread, you'll see that a half dozen of us, all with the same model of Mac, are having the same problem. Some of us have it in spite of having done clean re-installs. Some of us also noticed it cropped up after we updated to High Sierra. It seems probable to me that there's a software glitch in the OS, starting with High Sierra, that has a bad interaction with some of the computers in this batch; something about how the OS interacts with the hardware. It also seems likely that Apple will ignore the problem, because there aren't enough of us who have the problem (or maybe just not enough of us who notice it, and know enough to check the console for error messages) for it to be worth them devoting resources to it.

I found this post by someone who seemed to run into a similar problem, but with a different hardware configuration, who did a pretty thorough backtrace on the process:

https://objective-see.com/blog/blog_0x27.html

I am, alas, not computer literate enough to pick all that apart. But it seems related.

I have observed that this error is more likely to occur when my processor is under strain. It happens with or without my browser running, but it is more likely to happen when my browser is running, and to happen more often when my browser is running. It is more likely still to happen if I have a video window -- Netflix, Amazon Video, or Hulu -- open somewhere in my browser tabs, or if I have a movie paused on iTunes, running in the background.

I mostly use my Mac to write in Word. If I just run Word, with other applications closed (rather than running in the background) I can go for days or weeks without having this error pop up in my console.

Other threads talk about UI freezes in response to HDMI peripherals, with a similar error code.

I really think it's some kind of glitch in the load balancing for the graphics, and I think it's endemic to 15" Mid-2015 models.

I never use Chrome because of all the memory issues that it has. All I know is that I switched from Safari to Firefox over two weeks ago and I have not seen the freeze issues. Before that, it would have multiple times a day.

Just to possibly awake someone at Apple, I too believe Safari is the issue. After a reboot and only using Chrome for days/weeks I have not experienced the "IOAccelEventMachine2" freeze. I also 1000% agree that not using Safari is NOT a fix but a workaround. I am so frustrated that what seems to be an easy fix from Apple has not happened in the multiple OS updates starting with High Sierra (when the issue seems to have started) through multiple iterations of Mojave. I have been using Apple MBP's/PowerBooks for literally 28 years (since the PowerBook 170) and this issue (plus the $2k plus starting costs) is strongly discouraging me from buying another Apple laptop of any kind. Please Apple, any official response to the multiple postings of the same DOCUMENTED issue would be the professional thing to do!

Just do not use Safari app, or do not use it for longer period over the day and quite the app after usage. There are a range of other browsers which are useful you should switch to. Do not expect support from here...

I just received feedback from Apple through Feedback Assistant asking to gather "new sysdiagnose captured in macOS 10.14.5 18F132 within three days from the most recent crash. Old logs are missing gpu restart log." I let them know that I'm now running 10.14.6b1 trying to give feedback that way, and pointed to multiple sysdiagnose through the Feedback Assistant w/ the other feedback issue numbers. I'm hoping someone's seriously looking into this now.

Hopefully others here can also provide reports of the issue and sysdiagnose through https://feedbackassistant.apple.com/

After days without the problem, I launched Safari again with a minimal number of tabs open. This also ran for several days without a problem.

After opening a few tabs with WWDC session videos, the problem occurred again within minutes. I don't actually start any of the videos playing, and I have videos set to never auto-play, but they do still load some of the stream and show a player (presumably quicktime). The pause under these conditions seems to occur more often when I switch workspaces to a full screen app.

It has been six days for me since I stopped using Safari, and I have yet to see a freeze since then. So maybe the issue is related to Safari after all. Any one try this fix?

What temps does this App report around freezing time?

MacFansControl…

https://www.crystalidea.com/macs-fan-control

You can see dates of previous installs in System Report>Software>Installations.

Just as an update, I have not used Safari for the last 2 weeks, not a single freeze since.

I have this exact problem, turning off icloud fixed it.

Adding my confirmation of the same symptoms -- everything freezes for a couple of seconds. Macbook Pro Retina 15" mid 2015. Been going on for a while -- just updated to Mojave but same symptoms. As far as I can tell, it doesn't happen when I disconnect from wifi (no wired network as well). I can't reproduce the error or freezing with wifi off. Anybody else able to confirm that? Obviously not a workaround, just trying to better understand what is happening when I talk to Apple support.

Model Name: MacBook P

Unfortunately I just experienced back to back "virtual IOReturn IOAccelEventMachine2::waitForStamp" freezes while on battery power. There is a fundamental and inherent operating system software flaw with our particular hardware:

I believe there is a fix as this issue didn't seem to exist under Sierra. It feels a bit irresponsible to me that Apple continues to not officially respond to this issue in any way whatsoever. At least offer to look into the issue. I guess that would mean acknowledgment of an issue.