4 ms·

This still happens for me on OS X Sierra sometimes.

• polygot 9y ago
  Out of curiosity, is this bug related to CPU cache? I don't know really anything about how CPU's work internally, however. It just "feels like" it's applying a bunch of instructions very quickly but ignoring the internal clock if that makes any sense. For example, the CPU percentage counter in Activity Monitor was around 3,000,000. If there was a loop to increment the CPU usage counter, it sounds like it incremented it so fast that the thread that reset it didn't run since it wasn't scheduled to run (as it only runs every few seconds.) Again, this is just pure speculation and if anyone knows otherwise please let me know!
  • to3m 9y ago
    I very doubt it's anything to do with the cache, and that isn't an uneducated guess. But I've very doubted things before, and they turned out to be the case anyway, so why would you listen to me? My assumption was/is that it refreshes stuff on a timer. On each timeout it puts a refresh event on some kind of queue... and then somehow manages to fuck it up, and ends up having a bunch of these events to deal with all at once, rather than handling each one as it comes in with a sensible gap between each one. Well, sometimes it happens, and don't ask me how I know. But I have to say that you usually don't release it like that :(