Month 13 out of bounds

I deleted all the Plist entries in my Library/LauchAgents folder - and after five mins, so far so good. One program (Parallels) hasn't launched so I suspect a return to the problem when I start launching software that had plist info in this folder... but for now, my iMac is back to normal.

CheesedOffWithIT wrote:

I deleted all the Plist entries in my Library/LauchAgents folder

Generally speaking, LaunchAgents are not replaced when you launch the app. The are there to run background processes that are usually required by the app. Without them, you will probably see some functions no longer work or the app may become totally unusable.

indeed not a CPU problem but a functional one. Furthermore the console log has become a moving trashcan of messages making impossible to see the relevant stuff unless grep-ing or filtering continuously. not what a sane console should show. just sloppy sw engineering.

Not sure if this will help because I don't know if it's specifically your issue, but I noticed the 11.13.2 update wouldn't show up for me if my computer date wasn't current. Which it wasn't at first for me because the only way I could keep the UserEventAgent from launching and sucking up all the RAM and CPU was to set it before December.

I would contend that the revised console log has been useless without running specific search or filtered results since Sierra. I'm sure it functions well for developers who take the time to learn how to use it, but as a user I no longer watch the default scrolling window. I just wish it would open the same logs I need between reboots so I don't have to re-open them each time.

When I look at the default window now, I'm seeing an order of magnitude of other than error messages that are not related to Month 13 which make it unusable.

Hey

I have just got the same problem with my iMac. Running slow and a lot of the “month 13 is out of bounds”

Tried everything, changed the date, etc. Running the version 10.13.1.

Anybody found a solution?

I chased this down with Apple escalation and they assure me it is fixed in macOS 10.13.3 and later.

Since the problem stopped for me in early January, I have no way to test. Anyone still seeing it should see if the update fixes it.

Here is part of that report on my MacBookAir:

Does any of this make sense to anyone? Is there sone of these that could be causing the problem? Adobe??? Or that XProtectPlisrConfigData???

10.13.2 does NOT fix this. Still thousands of "Month 13 out of bounds"

Download macOS High Sierra 10.13.2

or

macOS High Sierra 10.13.2 Combo Update

Further, follow the link on for more details about the IOS 11.2 and what it fixed re: Dec 2 bug fix

Thanks! I just tried that... I changed the date to November 2, 2017, restarted the MacBook Air and thins seem to have returned to normal! I, too, wait for a fix from Apple.