We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hello,
I am currently using a µvision V5.26.2.0 and sometimes I can't save source file ( h , cpp ).
When it happened the pop ups window showing this message:
"Encountered a sharing violation while accessing {Path to me source file}"
The only one way that can change this behavior is to restart the µvision IDE.
Can I do something else?
I have reported this to support. They are working on it (they already had a case opened with the problem). I will get a notice from them once they figure this out I can also confirm that running in admin has no change. I have also just changed my development PC a week ago, the problem also occurs on this fresh installation (all files/projects are local disk, no SVN etc etc)
Afternoon Carsten,
Do you have Trend Micro antivirus installed and tmbmsrv.exe running?
Regards,
Rowland
Rowland, nope, none of them. In fact, the workstation right now is just a basic Win10 installation, nothing fancy (yet)
I'm not using Tread Micro, this is a self-induced resource leak, or race condition.
Oh my has this issue been resolved already?
I m using uVision 5.26.2 and in one of the occasions it destroyed my few hours of work.
How can this destroy hours of work ? In my case, when I get the "sharing violation" I just press CTRL-A and CTRL-C, closes uVision, opens it again (the file that had sharing violation even has the focus after uVision is re-opened) and press CTRL-A and CTRL-V, and all is on track again ?
I do the same most of the time.
But in that occasion, I was in a rush to finish off work and leave the work place.
The sharing violation happened to not one but all the .H files opened. It will not show the error message again if you press 'save all' button unless you click on the individual tab in the editor again.
So in the end I missed saving one of the files and went home. Guess what I found out the next day?
I meant this kind of bug is quite in-tolerable to me.
Ah, that figures! I have (so far) only had a single error at a time, probably because CTRL-S is so firmly layered in my fingers ;) But agree, it would be VERY nice if the bug could be removed ASAP!
Hello Carsten,
Please open an support ticket with Keil, and they can try to get you an early release of the fix.
Kevin, I already did at Nov 5th (Sankalp is on it) Looking forward to get a fix for this one :)