Odd MPLAB X issues - is it only me?

I'd like to know if anyone else is having the same problems with MPLAB-X so I know if it is my system or not:
 
Issue #1: About 20% of the time when I try to clean and build, it fails because some of the files that MPLAB generates are "locked". I have to use a file unlocker tool to delete them before I can work any more. I can't seem to find any specific things that cause this. But it is very frustrating and time consuming!
 
Issue #2: If I make a minor code change and then try to use 'Debug Main Project', what I get is the previous version - my change is not compiled in. I have to hit 'Clean and Build' every time before I can debug again.
 
Issue #3: About once an hour or so, I will be editing a file and the MPLAB-X program just disappears. It doesn't close, it just goes away. The process is just gone! Files are not saved but neither are they corrupted. I can run it again and it wakes up just fine and works just fine. Sometimes it will work for a few hours before this happens again.
 
My system is VERY solid and doesn't exhibit any issues like these doing anything else, nor did it have any problems with MPLAB-8. I uninstalled 5.45 and then reinstalled the whole thing, but the issues remain.
 
If anyone else has seen these behaviors please let me know.
 
Topher
 

ChrisFox
Issue #2: If I make a minor code change and then try to use 'Debug Main Project', what I get is the previous version - my change is not compiled in. I have to hit 'Clean and Build' every time before I can debug again.
 

I am absolutely sure I have seen that but can never recreate it on demand and assumed it was a case of PEBKAC, but having seen someone else report it, I am not so sure.
 
I am running 5.35 with XC8 and PICKit4.

I am about to double my RAM - maybe that will help speed things up. When I get files locked, I can't build again. Builds fail because the files are locked. I have to run an unlocker program and delete them all before I can do anything else. It's a real PITA.
Thanks for the remarks!
Topher

I still can't do the Build and Run without doing a Clean and Build first every time. If I click Build and Run it just runs the code before my changes. It's like it doesn't perform the Build part and runs the previous version.
 

I am still using a Windows7 pro 64-bit but what I did to get MPLABX to almost always be sane is:

1. Install a piss-pot of real memory (went from 6GB to 24GB)
2. Boot from SSDD and have MPLABX and compilers installed on that drive

MPLABX seems to behave badly in the build and run on the In-Circuit-Debug.
 
I almost always have to end the debug session and wait for MPLABX to actually kill the debug process before starting another session.
 
Also the more JRE crappplets that are running seem to cause issues. For example I like GitKraken, but MPLABX seems more prone to behaving badly when GitKraken is idling in the background.