I also ended up encountering same issue. But I guess this could be a bug, because this doesn’t happens with “SceneTexture:PostProcessInput0” node. I tried to explain my point of view on another post: User Scene Texture BUG Happens by Changing Resolution of Game
Here is what was happening in my case on eigenvector pass:
