Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

[Windows 7] Security Error when saving file #5079

Closed
Cyrene opened this issue Sep 5, 2013 · 12 comments
Closed

[Windows 7] Security Error when saving file #5079

Cyrene opened this issue Sep 5, 2013 · 12 comments
Assignees

Comments

@Cyrene
Copy link

Cyrene commented Sep 5, 2013

System:
Windows 7
Sprint 30

Description:
I have been getting this error since at least sprint 26 where when I ctrl+s while Live View is active, Brackets will toss up this dialog saying a security error has occurred and I am not allowed to save the html file.

errorcapture

Expected:
Normal saving of file without issue using ctrl+s quick-key command.

Actual:
I have found this happens after I have already been editing and saving the document during the same session.

Workaround:
"Save As" a new document. Once the file is tossing up this error in Brackets, I can no longer save changes to it - I have to delete the effected file. I can't even use a different program (see below).

securityerror-otherapp

@ghost ghost assigned jasonsanjose Sep 16, 2013
@jasonsanjose
Copy link
Member

@Cyrene Is the path to this project under C:\Program Files? If it is, we can't write to the path due to windows security. See #1577.

@Cyrene
Copy link
Author

Cyrene commented Sep 16, 2013

Brackets Sprint 30 is installed in the C:\Program Files (x86) as by default, but the actual project files are in C:\User\file\file\Desktop..

What's odd to me is that it seems to be fine with me saving and working for a while and then it stops and throws up that error.

@JeffryBooher
Copy link
Contributor

A sharing violation means that some other process has it locked for exclusive access. @Cyrene Do you have any other programs running when you're working in brackets with these files?

@Cyrene
Copy link
Author

Cyrene commented Sep 19, 2013

The only other application that would be accessing those files while I'm working is Firefox v24.0.

@JeffryBooher
Copy link
Contributor

@Cyrene can you download Process Explorer from Microsoft, and the next time this happens, run Process Explorer and do a "Find > Handle or DLL" and type in the filename that gives you the sharing violation and look to see what other processes have that file locked.

@JeffryBooher
Copy link
Contributor

Taking this one from @jasonsanjose

@ghost ghost assigned JeffryBooher Sep 19, 2013
@Cyrene
Copy link
Author

Cyrene commented Sep 19, 2013

@JeffryBooher will do and get back to you

@ToonVo
Copy link

ToonVo commented Sep 28, 2013

I had the same problem with brackets 31. According to Process Explorer it was caused by taskhost.exe. After closing the explorer (from where I launched Brackets with "Open with" context menu option) I was able to save again. The file was not located in C:\Program Fiiles by the way.
It seems you can open a file from the explorer but you have to close it afterwards.
Or am I doing something wrong here (windows settings or whatever)?

@peterflynn
Copy link
Member

@ToonVo taskhost.exe is a generic container for all background services. The next time you see this problem, you can try to get more details about what's running inside taskhost.exe:

  • Hover over the "taskhost.exe" filename. The tooltip should have a list of "Tasks"
  • Or... Choose View > Lower Pane. Look in both the DLLs and Handles views, and see if there are any clues as to what it's running (unfortunately this is not always easy to make sense of).

@JeffryBooher
Copy link
Contributor

@Cyrene we implemented recently a new file system layer which hopefully solves your issues but since we haven't heard from you in 6 months on this issue, we're going to close this as not a bug. Let us know if you continue to see problems saving files.

@peterflynn
Copy link
Member

I doubt the new FileSystem stuff would change anything about this bug, but it also sounds like this wasn't our issue -- if some other app has the file locked, there's nothing we can do to write to it (as seen in original report where other apps are blocked too).

@AndrewMcDowe
Copy link

I'm very late to this party but I fixed this by checking if the folder was Read Only. Try switching that off and see if it works.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants