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

kecinzer

macrumors 6502a
Original poster
Oct 19, 2015
671
386
Czech republic
I didn' find any trhead about bugs in 10.12.4 beta 1.
I installed it on my MacBook Pro 13" mid 2014 and experiencing this bugs:

1) Every morning for about 30-60 minuts I see kernel_task process that causing that my mouse pointer is snatchy. I never experienced it before.
2) There is problem with gestures in Safari. I almost can't do back/forward gesture on touchpad or magic mouse. Reboot solved this problem!

Can someone confirm this?
 
Last edited:
Yes, I'm seeing the kernel_task process using 30-70% CPU which causes a noticeable slowdown - seeing the same issue with the mouse pointer. I just restarted and it calmed down after a few minutes. Don't know what triggers it.
 
1) Every morning for about 30-60 minuts I see kernel_task process that causing that my mouse pointer is snatchy. I never experienced it before.

I'm seeing something worse than that. Beachball locking up the entire interface. Nothing using much cpu after ssh in from another mac. Happened this morning, and yesterday morning as well, but not during the day/evening. Night shift on, both times happened about 20mins before sunrise though. Shutdown rather than leaving it for 30-60 minutes though. Has problems detecting monitors properly during that time frame if I reboot.
 
I didn' find any trhead about bugs in 10.12.4 beta 1.
I installed it on my MacBook Pro 13" mid 2014 and experiencing this bugs:

1) Every morning for about 30-60 minuts I see kernel_task process that causing that my mouse pointer is snatchy. I never experienced it before.
2) There is problem with gestures in Safari. I almost can't do back/forward gesture on touchpad or magic mouse. Reboot solved this problem!

Can someone confirm this?
My touchpad on 10.12.3 gestures have issues about 2 times per week and I have to reboot. I have the 13" MBP TB
 
Mouse motion is not smooth at all as soon as Night Shift was activated at sunset.
[doublepost=1485469164][/doublepost]Mac restart didn't fix it.

I came here to post this. Night Shift is nice, but still badly optimized. On my MacBook Pro 2016 (15) you yan see the mouse pointer stutter, and every single animation slightly stutters. Scrolling in documents and safari is also slower.

I know it's a beta, but this has to be their priority or this feature will never be used
 
I am on the Public Beta 1. My Magic Mouse 2 does not work even though it says 'connected'. Reboot did not help.
 
I came here to post this. Night Shift is nice, but still badly optimized. On my MacBook Pro 2016 (15) you yan see the mouse pointer stutter, and every single animation slightly stutters. Scrolling in documents and safari is also slower.

I know it's a beta, but this has to be their priority or this feature will never be used
And I'm on public beta. I thought public betas were supposed to be "less buggy" than dev betas.

By the way, Mac restart alleviated the stuttering somewhat, and it goes away completely after a while.
 
And I'm on public beta. I thought public betas were supposed to be "less buggy" than dev betas.

By the way, Mac restart alleviated the stuttering somewhat, and it goes away completely after a while.

Public Beta is the same build as the Dev Beta usually. Its purpose is to provide the current version to a wider audience for testing while at the same time eliminating the chance of an uproar caused by a significant bug. If the bug happens during the short Dev-Beta-only phase, there will be less of an uproar.

And yes, I restarted, this is the first thing I always do. But it didn't get better. Actually I restarted before I even tested nightshift this morning (before the sun was up)
 
Public Beta is the same build as the Dev Beta usually. Its purpose is to provide the current version to a wider audience for testing while at the same time eliminating the chance of an uproar caused by a significant bug. If the bug happens during the short Dev-Beta-only phase, there will be less of an uproar.

And yes, I restarted, this is the first thing I always do. But it didn't get better. Actually I restarted before I even tested nightshift this morning (before the sun was up)
So basically, public betas are only to protect users from deadly bugs, not harmless ones like stuttering during night shift. Oh well.

By the way, more than likely stuttering never went away. Instead my eyes got used to it making my brain think it went away. Kind of like the placebo effect.
 
  • Like
Reactions: NoWayBehind
Night Shift on, public beta. No issues with gestures, stuttering, or artefacts. I'm on a MBP early 2015.

EDIT: Low framerate when Night **** is fully in effect.
 
Last edited:
Installed 10.12.4 Beta 1 this morning.

WindowsServer which is the service for applications to use the graphics card has extremely high CPU usage when you run Parallels.

This causes parallels to lag extremely bad, and while Parallels is running, OSX runs extremely bad. 2015 rMBP.

Quitting Parallels immediately brings the performance back, lovely.
 
Last edited:
When I try to play mkv files, gatekeeper kicks and, and it has to verify every file I try to run. Larger files take more then a minute to actually run on my rMB2016.

Anyone else has this problem?
FilaVault is off, as is firewall. Gatekeeper is off, used terminal for that. Never experienced gatekeeper showing up on files that are not applications...
 
Installed 10.12.4 Beta 1 this morning.
WindowsServer which is the service for applications to use the graphics card has extremely high CPU usage when you run Parallels.
This causes parallels to lag extremely bad, and while Parallels is running, OSX runs extremely bad. 2015 rMBP.
Quitting Parallels immediately brings the performance back, lovely.

I'm not seeing WindowsServer using high CPU on my machine (2016 MBP w/Touchbar) with Parallels. I'm running Parallels v12.1.3. It runs around 3~10% with just the desktop open. However, The Parallels VM itself uses a lot of CPU but that's normal.
 
When I try to play mkv files, gatekeeper kicks and, and it has to verify every file I try to run. Larger files take more then a minute to actually run on my rMB2016.

Anyone else has this problem?
FilaVault is off, as is firewall. Gatekeeper is off, used terminal for that. Never experienced gatekeeper showing up on files that are not applications...

MKV files are video files, what player do you use?
 
@cswifx

I know. That's what bothers me, since Gatekeeper never fires up on regular files. I'm using VLC. Tried deleting VLC and all of it's files on system, then reinstalling, but that didn't help at all. I guess I'm just waiting for the next update, that hopefully resolves this annoying issue :)
 
@cswifx

I know. That's what bothers me, since Gatekeeper never fires up on regular files. I'm using VLC. Tried deleting VLC and all of it's files on system, then reinstalling, but that didn't help at all. I guess I'm just waiting for the next update, that hopefully resolves this annoying issue :)

Just a thought... See if it's actually a '.mkv.app' file sneakily trying to mask as a video file.
 
  • Like
Reactions: macintoshmac
dont understand how people dare to install betas from apples when even the release versions are a catastrophe :D
 
dont understand how people dare to install betas from apples when even the release versions are a catastrophe :D

no catastrophes here. and all software has bugs; did you not know that? :rolleyes:

have been running the betas for several years. have had issues, and have had them resolved (not always right away). am into sierra, having a mostly-good experience. so far, 10.12.4 public beta's been ok here (one cursor issue, fixed with a reboot).

betas are betas, there's no reason to run them unless you're prepared to sweat out the bugs...
 
  • Like
Reactions: cswifx and Jayderek
Just a thought... See if it's actually a '.mkv.app' file sneakily trying to mask as a video file.

Nope. Happens with every mkv file. Even my old files go thru the same thing. Googling it I found a couple of posts for older OS X beta versions that had the same problem. It's a bug that's gonna get sorted out, I just hope that they sort it out in the next beta release :)
 
dont understand how people dare to install betas from apples when even the release versions are a catastrophe :D

I literally signed up for beta on both my MacBook and iPhone when I got my first iPhone, had no major phone breaking issues at all, and Apple is generally responsive when I report bugs (especially recently).
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.