Month 13 out of bounds

Not sure why you are telling me this. I'm well aware that the "Month 13 out of bounds" messages in the console are High Sierra only and I can see them when I switch to Console, but they are not causing any issue for my iMac nor for any of the several hundred others that I correspond with daily on macOS problems, so under no circumstances would I consider reverting to Sierra at this time. Apple has informed me "The bug is causing a log line to be generated, and it does not otherwise prevent or modify any functionality."

Perhaps I missed it, but are there other indications of a problem with your MacBook?

I'm having to run a script to kill the UserEventAgent process otherwise it uses all my Physical Ram and then goes into VM, 99.2% of CPU rendering my iMac useless. This only started AFTER the obviously rushed out security and file sharing patch.

Apple are aware of an issue and are 'supposed' to be looking into it. If it's still the same at the end of the week. I will be wiping and returning to Sierra. No one I know on Sierra is having issues, everyone else I know on High Sierra has issues on at least one machine. Over to Apple to sort it out. I had to send them logs yesterday, whether it helps I'm not sure.

P. Phillips wrote:

it would seem Apple created this >> therefore Only Apple can fix it

If they admit it :-) !

Something to think about. New versions of iOS, tvOS, and watchOS

were released as well as a new Xcode version to support the above

and 10.13.2. Perhaps they had second thoughts about getting serious

about QA before releasing 10.13.2?

if they admit it :-) !

Something to think about. New versions of iOS, tvOS, and watchOS

were released as well as a new Xcode version to support the above

and 10.13.2. Perhaps they had second thoughts about getting serious

about QA before releasing 10.13.2?

Admit -- not holding my breath. Yes, maybe serious about QA before 10.13.2 but that too am not holding my breath

Oddly and amusingly...had Apple call me back today. Yes I know you are in here looking as the 'engineers' told me try...everything that has already been mentioned in here, pretty much word for word. And no they don't work, except the shell script that was helpful and does work as it continually kills the process.

Back to Sierra for me.

For anybody interested in seeing the coding that appears to be causing this fault see the Apple Code linked to it in this Tweet by a German Software Developer at elgato.com. It's in the 'ASSERT_VALID_MONTH' code.

So now, Dec. 6, as I wait for something from Apple to fix this, I have a temporary workaround that works for me. I'm retired and don't depend on the MacBook Air for my livelihood so I can afford to wait... maybe until January 2018 for the date to change! I've found that by closing the MB Air (that is, just moving/closing the screen to close, NOT shutting down the system) turns off the fan, which for me is the most annoying (is this "sleep mode?). Then periodically through the day I open the hood and check email or do some surfing.

Same story here, had to run the script, rebooted and forgot to restart it, no CPU or RAM spike and no UserEventAgent. Nothing has changed or been updated by me and nothing I can see overall has changed. Yet it's stopped?

I've removed Disc Doctor, Evernote and Adobe Acrobat Reader. I don't know how to delete the 2 *ConfigData items. Nothing's changed. Fan still running (too)fast and UserEventAgent is ticking along using 98+% of my CPU. [Oddly, when I deleted the Adobe Acrobat Reader the UserEventAgent slowed down to around 60% for about 5 min. before returning to the (ab)normal 98% consumption Thought I was on to something for a brief moment... felt good!

At first I couldn't see the update. Then it appeared. I've installed it and the UserEventAgent is behaving AND (so far) the fan isn't running wildly! Of course, I'm not sure how or what they figured out but things are hunkey-dorey for now. Thanks to everyone's input... it's been a trip! And maybe this thread helped to make a difference!

The 10.13.2 update seems to have fixed at least the major issues. Like others, I still see the "Month 13 out of bounds" error in console, but it's showing up as either a console error or loginwindow error now. Doesn't show anymore as a UserEventAgent error. So it seems they've fixed it so it at least doesn't launch the UserEventAgent which was what was sucking up the CPU and RAM. Might not have solved the underlying issue, but at least it's not crippling my computer anymore and I don't have to worry about the other issues that result from backdating my computer to November 🙂.

Hi there

Suffering the same issue re UserEventAgent.

No opportunity to download latest Hig Siera - App Store says my iMac is up to date.

This is really ruining my business productivity!

Any ideas where to get this silver bullet fix 10.13.2?

Thanks in hope.

michelefromwassenaar wrote:

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

I never said that it did. What I said was that the high CPU/RAM use was fixed for everybody who has responded. The Month 13 out of bounds is just a log entry that does not impact functionality, according to Apple Engineering.

Are you having issues?

michelefromwassenaar wrote:

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

I never said that it did. What I said was that the high CPU/RAM use seems to have been fixed for everybody who has responded. The "Month 13 out of bounds" is just a log entry that does not impact functionality, according to Apple Engineering.

Are you having any other problems?