The new V2.2 introduces a Shaders “Edit and Continue” ability which allows you to Edit, Save and Compile Shaders source code, Link and Validate Programs “on the fly”.
This feature saves developer time required for rebuilding and running again the developed application.
It is very easy to crash if you load an old project workspace.
If you add some counters to the performance dash board, click OK then bring the Add dialog back up, remove the counters, and the app crashes.
(note that this only happens if you do the adding and removing via the ‘+’ on the performance daskboard.)
I seriously think you need a way to flag what shaders are currently being used. In non-trivial apps there can be 100’s of loaded and idle shaders and finding the ezact one to edit can be a real pain. (perhaps some “last used frame count” for the shader as used in GLIntercept. - no way to “flash” the in-use shader?)
We managed to locate and fix the problem you reported.
The fix will be released in our coming bug fix version, that will probably be released within a week from today.