Steps to reproduce
- View https://samples.dundas.com/Dashboard/c397551a-e1f0-48e2-bb22-fa0def388063?e=false&vo=viewonly
- Lock or disconnect from the Windows session (recommended)
- Wait for an extended period of time without logging back in (recommended)
Steps 2-3 may not be necessary, but the results may be different or less reliable without them: we have seen memory consumption going up and down, or going up less sharply.
The attached graph tracks only “working set” by mistake, but private bytes and working set have been similar.
Comments and activity
Nothing to see here! No one has commented on this issue yet.