Sanderxpander
I could send you the project if you like. Unless you'd like to insist that I'm lying.

No I'm not saying anything about your truthfulness. I would hope you wouldn't take it that way. I have never seen this behavior in all the years I have had Sonar. Therefore, I believe it to be user error. As I said I don't understand the mechanism that would do that. That could be my short coming.   

FWIW, I don't understand the mechanism that would do it either, but I know how to close a plugin and save a project. I've had weirder things happen with project corruption, basically it seems a state is not being saved/overwritten correctly (a screenset?). That's why I thought in that direction, though I'm not hung up on the term "project corruption".

Double post

I know for myself whenever I have projects created in an older version that I open in several other newer versions they start exhibiting odd behaviors. There's not much you can do about it other than recreate the project from scratch in a new version. Luckily most of these oddities are not show stoppers.
 

Just wondering... are the GUIs still open regardless of which screenset was active before closing the project?
 

Check your screen sets to see if they were inadvertently locked, with the plugin windows opened.

js516
Check your screen sets to see if they were inadvertently locked, with the plugin windows opened.

Very insightful. Even if it is not the case here it is still a brilliant idea.

 

js516
Check your screen sets to see if they were inadvertently locked, with the plugin windows opened.

Glad I skimmed through the posts because I was gong to suggest exactly the same.

1. Unlock screenset
2. Close plugin gui's
3. Lock screenset
4. Save project