We recently upgraded from 8.1.16 to 8.3 and hadn't had this issue in the past. We use a home screen that has button presses of system.util.retarget() to redirect to different projects for different areas. Many people only use this to go to one project, but we have super users who go back and forth between different projects, back to home, etc. After 3-4 retargets, I believe we are hitting a memory limit and many of the metrics display the incorrect tag values or are grayed out. I read that there could be memory allocated each retarget, eventually running out of space, and that restarting may be the only solution. Has anyone ran into this, and are there any solutions outside of making those super users close and reopen their clients manually each time they go between projects? Thanks!
IIRC, retarget doesn't restart the JVM, so any memory settings on the initial project will carry forward to any others, ignoring the project-specfic settings for those.
I also recall there being some leakage related to retargeting, but I don't recall the specifics. (My clients use separate desktop shortcuts for Vision, not a common "home" project.)
I think we fixed this at some point mid-stream 8.1; there's also a mechanism to force the JVM to relaunch in case you've moved between gateways with different requirements, such as Java versions.
@douglas.lane I would consider this a bug; could you report it in to our support department officially?