After promising a fix for 2 months I found out the patch they created was for view 5.2. I upgraded today to 5.2 and installed the special patched version of the view agent and verified it does fix the issue. You will have to open a support ticket to get the patched 5.2 agent. A new version of view was released that you could upgrade to as well (not sure how stable it is though) and that will have the fix built in.
↧