XCode console flooded with "Invalid timestamps for HID response delay" messages on a hello world app

I tested a simple MacOS app, with storyboard, with Xcode 13.0ß4, with MacOS11.5.

I do not get those messages, just a few Metal warnings :

2021-08-01 18:12:49.944683+0200 Simple MacOS test[11072:1323345] Metal API Validation Enabled
2021-08-01 18:12:50.073140+0200 Simple MacOS test[11072:1323345] MTLIOAccelDevice bad MetalPluginClassName property (null)
2021-08-01 18:12:50.074332+0200 Simple MacOS test[11072:1323345] +[MTLIOAccelDevice registerDevices]: Zero Metal services found

I found references to the problem since 2017 when using Cordova. Is it your case ?

h t t p s : / / github.com/immersive-web/webvr-polyfill/issues/201

Otherwise, that could mean that you have timestamps out of sync. Do you have some antivirus installed ? Hope this could help:

https://discussions.apple.com/thread/251314646

Thanks Claude. I am not using Cordova (or anything similar), and I do not have any antivirus installed.

In my case, the solution to the problem was to remove the Vox Preferences plugin. Just remove it and messages gone.

Same problem since I switched to an M1 Mac.

I have this problem and it's everywhere. I can click around in Console.app and it says Console itself is generating the messages. If i click around in Safari, it says Safari is generating them. I can build a binary using GLFW from the command line and it will tell me that THAT process is generating the error. It basically happens with every window, any time I click or sometimes even just moving the mouse/trackpad cursor. Console hints that it has something to do with /usr/lib/libspindump.dylib. (see screenshot)

I'm a developer; I have homebrew installed. There might be something going on with something installed there, but I have no idea what. I can't NEVER remember a time where I WASN'T seeing this show up in stdout / Console on this machine, a 2021 M1 Macbook Pro. (see machine specs screenshot).

Dear all,

I had the same problem here. There are only few answers to this on the web, but the most common one is relevant and worked in my case:

1/ start in safe mode. If the messages disappear in safe mode,

2/ restart in normal mode, move all non-system extensions (/Library/Extensions), Launchagents (/Library/LaunchAgents) and Launchdaemons (/Library/LaunchDaemons) somewhere else and restart again. If the messages do not appear,

3/ move back some of those files to their initial position, restart, check console, continue moving back etc... until you find which extension, Launchagent or Launchdaemon is responsible for the invalid timestamps

All the best,

Alexis