I've noticed this only on long running vims in my Linux server. I've narrowed down the E484s to lines of my vimscript that call
I just wonder if there is a way to deal with this because so far i have just been closing and restarting vim if this happens. But since the problem is so specific, it would be nice if it could be addressed so i can continue to use the running instance.
It's tricky to test and iterate on this because it takes at least 3 weeks before a vim instance gets into this state.