-
Notifications
You must be signed in to change notification settings - Fork 24
NS_FILE_IS_LOCKED on FF27 / Win7_64 #16
Comments
The error message suggests that the file is locked by another process. Possibly an instance of Firefox that crashed? Is the file on a network drive? |
hello jeremy, it is on a usb stick, fat32. no other process is actively accessin the fule. on ff 18 or 19 on the same machine it works. Mit freundlichem Gruss, Am 10.02.2014 um 19:01 schrieb Jeremy Ruston [email protected]:
|
Thanks @steady286 - does it work OK using files on your main hard drive? |
jeremy, |
Hi @steady286 I think it is probably an issue with recent versions of Firefox. It might be worth checking with the latest nightly of Firefox to see if you fare any better? |
I have something like this. It only happens with a large tiddlywiki. I deleted a couple of tiddlers and then it stopped happening. Is anything in tiddlyfox size-dependent? Also, where is the permission stored (such that the first time, tiddlyfox asks permission, and after that, it doesn't) ? |
Wow, interesting. We've not come across anything like that before. Can you reliably duplicate the problem? What size is the wiki file?
TiddlyFox uses Firefox's built-in permission manager: https://github.com/TiddlyWiki/TiddlyFox/blob/master/content/overlay.js#L155 I don't think that Firefox provides a user interface for these permissions. |
Thank you, Jeremy, Unfortunately (?) it was not fully replicable. It repeated on a renamed Actually I stress FF a lot, and I think it has memory leaks or something The tiddlywiki was about 10 megabytes; Firefox memory at 2 gigabytes. I suspect the permission is stored in the mysql settings database inside On 1/6/2015 6:29 AM, Jeremy Ruston wrote:
|
Content cannot be saved using the setup named above.
Error Message is:
[Exception... "Component returned failure code: 0x8052000e (NS_ERROR_FILE_IS_LOCKED) [nsIFileOutputStream.init]" nsresult: "0x8052000e (NS_ERROR_FILE_IS_LOCKED)" location: "JS frame :: chrome://tiddlyfox/content/overlay.js :: <TOP_LEVEL> :: line 98" data: no]
The text was updated successfully, but these errors were encountered: