Skip to content
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.

NS_FILE_IS_LOCKED on FF27 / Win7_64 #16

Open
steady286 opened this issue Feb 5, 2014 · 8 comments
Open

NS_FILE_IS_LOCKED on FF27 / Win7_64 #16

steady286 opened this issue Feb 5, 2014 · 8 comments

Comments

@steady286
Copy link

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]

@Jermolene
Copy link
Member

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?

@steady286
Copy link
Author

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.
best regards
gerhard

Mit freundlichem Gruss,
Gerhard Dutka

Am 10.02.2014 um 19:01 schrieb Jeremy Ruston [email protected]:

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?


Reply to this email directly or view it on GitHub.

@Jermolene
Copy link
Member

Thanks @steady286 - does it work OK using files on your main hard drive?

@steady286
Copy link
Author

jeremy,
on a hard drive it works... magic !
is this some kind of security feature?
at least on linux/ff 25.0.1 it also works on my usb - stick...
best regards,
gerhard

@Jermolene
Copy link
Member

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?

@Ca1vino
Copy link

Ca1vino commented Jan 5, 2015

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) ?

@Jermolene
Copy link
Member

Is anything in tiddlyfox size-dependent?

Wow, interesting. We've not come across anything like that before. Can you reliably duplicate the problem? What size is the wiki file?

Also, where is the permission stored (such that the first time, tiddlyfox asks permission, and after that, it doesn't) ?

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.

@Ca1vino
Copy link

Ca1vino commented Jan 8, 2015

Thank you, Jeremy,

Unfortunately (?) it was not fully replicable. It repeated on a renamed
copy of the file, and on a Firefox restart, but not a computer reboot...
I haven't seen it again, luckily.

Actually I stress FF a lot, and I think it has memory leaks or something
else... it eventually hangs or crashes.

The tiddlywiki was about 10 megabytes; Firefox memory at 2 gigabytes.

I suspect the permission is stored in the mysql settings database inside
the Firefox profile. If so, a Firefox add-on can be used to browse /
modify the data.

On 1/6/2015 6:29 AM, Jeremy Ruston wrote:

Is anything in tiddlyfox size-dependent?

Wow, interesting. We've not come across anything like that before. Can
you reliably duplicate the problem? What size is the wiki file?

Also, where is the permission stored (such that the first time,
tiddlyfox asks permission, and after that, it doesn't) ?

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.


Reply to this email directly or view it on GitHub
#16 (comment).

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

3 participants