Month 13 out of bounds

Hello

I've outlined the problem here

There is a good solution by Ckacmaster here

Additionally, I believe the issue resides in loading plist files; UserEventAgent attempts to use plist files and makes an error because of it which causes high RAM and CPU usage.

Good luck

Eric Root wrote:

I would uninstall Intego. It tends to interfere with the computer's operation while providing minimal to no benefit unless you work with Windows files.

Actually, Intego only developed macOS software, so it doesn't really help with Windows files.

rd_8888 wrote:

but still get the RAM issues.

Don't worry about RAM use. Since OS X Mavericks, the memory manager attempts to make maximum use of RAM and attempts to keep it full at all times to prevent having to prevent having to access drives to reload code and other files that are frequently needed. It uses compression and cache monitoring to make room for anything new that it needs.

To check open Activity Monitor to the Memory tab and look at the MEMORY PRESSURE graph at the bottom. If it stays green all the time there is no RAM issue. Red normally means buy more RAM, but that's not applicable in your case.

I have to worry about the RAM issue. UserEventAgent hits 1 GB of RAM usage in 27 seconds of running, and 2 GB in 54 seconds. It's pretty linear. Memory pressure turns orange/yellow in 3 min 43 seconds and red in 5:24. I force quit it at that point because I have to get work done on my computer tonight. At that point, UserEventAgent was using 10 GB. The most I saw prior was > 30 GB, and that's when it was filling up my disk with swap files and making my computer completely unusable.

I purposely waited to respond until the month 13 issue was under control. I fully understood that RAM issue.

I was specifically referring to your comment that ClamXAV (I assume you were referring to it's Sentry process) was using too much RAM. It needs to load the full signature database into RAM as it needs constant access to it. If it was left on your drive it would slow everything down each time a new file was created in the watch area. I have not observed that to be an issue for any ClamXAV user unless they were truly RAM starved.

But while we are on the subject of Anti-Malware software, it's never a good idea to have two background scanners active at the same time. Manual scanning, one at a time is fine, but with background scanners watching the same areas, they fight over who gets to scan the same file and tend to interfere with each other and unnecessarily slow your computer environment in the process. I haven't used Intego for a number of years, so I don't know whether you can disable the real-time or on-access scanner but you evidently know you can do so for ClamXAV by disabling Sentry use in the preferences. That will prevent all significant ClamXAV background processes except scheduled signature updates and / or periodic scans, if you have them enabled.

There is no problem here other than the month 13 problem. I discovered the month 13 problem when I tried to build an application that i'm in the process of making. I discovered two things: 1. MacOS seems to think December is the 13th month of the year, rather than the 12th month. This throws errors because there is no 13th month, so whenever a process that needs to use the date runs, it can't understand the value of 13; hence "Month 13 is out of bounds". 2. In my application, I needed to use plist files to load various elements of my application. Though the application did not crash, it wouldn't load any of the data due to the month being 13. This is also what I discovered with UserEventAgent, and what is explained here. Therefore it makes complete sense to me that when ClamXAV attempts to access it's database and can't due to the month 13 error, it reacts similarly to UserEventAgent and spikes RAM and CPU.

HudsonGraeme wrote:

it makes complete sense to me that when ClamXAV attempts to access it's database and can't due to the month 13 error, it reacts similarly to UserEventAgent and spikes RAM and CPU.

I held off responding until I could get back to running High Sierra to check a few things.

First off, there have been no reports to the developer of excessive RAM user by ClamXAV Sentry since the #month13 issue began. In fact, the OP's observations here are the first I've found anywhere. Now that I'm in macOS HS and observing "Month 13" errors in Console I can see that none of them are showing up credited to either ClamXAV Sentry or clamd. Activity Monitor indicates that the sum of those two processes are a shade over 600MB RAM. Further checking reveals that neither involve the user level's UserEventAgent in any way.

I do see a wide variety of other Apple & 3rd party apps & processes are involved and agree that there does seem to be a connection with the UserEventAgent. I would conclude that with all High Sierra users seeing the "Month 13 is out of bounds" error but only a small fraction having CPU/RAM issues that it's the log entries are Apple's problem but the other issues are 3rd party dependent. That's also what I'm hearing from Apple.

MadMacs0 wrote:

I do see a wide variety of other Apple & 3rd party apps & processes are involved and agree that there does seem to be a connection with the UserEventAgent. I would conclude that with all High Sierra users seeing the "Month 13 is out of bounds" error but only a small fraction having CPU/RAM issues that it's the log entries are Apple's problem but the other issues are 3rd party dependent. That's also what I'm hearing from Apple.

Totally agree.

The RAM spike seems to be a totally different issue, caused by third party software.

I have had this issue since I rebooted on 2nd December...stupidly.

RAM and CPU usage go through the roof, at one point usereventagent was using 103GB of RAM and VM. Changing the date back to November worked, but now I can't use certain programs as they check my subscription, eg Lightroom and Photoshop

Apple you need to look into this. My Macbook is fine, my imac however is now unusable. Is there an easy way to downgrade to OS Sierra?

As I see it there are two options. Hold off downgrading until a fix is in place for HS or downgrade. The second is not so easy even if one has the original Installation file of Sierra. Would have to create bootable installation USB, boot from it, erase internal HD / SSD and reinstall Sierra and then either migrate back personal stuff or install all apps from scratch.

Every one running High Sierra needs to check their machines. I have

seen this error pop up in console on all four of my Macs. It is not

creating the debilitating situation that those here say they are having,

but it does occur!!

All four Macs have dramatically different installations of apps and usages.

The fault is not seemingly anything 3rd party but endemic of High Sierra.

The one is a MacMini used as a server and only has Server, iTunes, and

native Apple apps and it is showing the error!!

Yet another "oversight" from Apple in High Sierra?

allanlawphoto wrote:

Spoke to engineer at Apple "unaware of an issue" but have asked to me send them log files....fingers crossed!

Oddly macbook is fine, imac however about to get thrown out a window.

Watch Console in the MacBook. It will pop up the message.

It may not be spewing, but it will pop up. As I said it is there

in all 4 of my Macs but is not debilitating them.

I have pretty much verified that it is a High Sierra issue because

the error shows up in Console when booted into Safe Mode which

disables a 3rd party nonsense.

So, this is hiding on all machines but with the right combo of

hardware and apps, will go ballistic!

Makes one wonder how many "performance issues" are actually related

to this.

Good luck.

I wouldn't call this a 3rd party issue when OS api's break that other apps utilize. In my case, launchd is Apple too.

I got off of the phone with Apple but it was just a regular customer service rep - they were not equipped to really deal with the issue and had not even read up on the case notes supplied. I have no other meaningful way to reach out to Apple to discuss this issue with a technical person. If anyone does, feel free to point them in my direction.

Can say 100% no 13 month issues running iMac with 10.12.6 but 12' Retina MacBook with 10.13.1 and Security and File Sharing Patches installed - Console overwhelmed with 13 month error messages. Considering downgrading MB back to 10.12.6 and wait until 12.13.3 or maybe 10.13.4 before upgrading if at all.