[TWC] Can't save TW in FireFox - (with dirty work-around)

342 views
Skip to first unread message

Bob Flandard

unread,
Oct 26, 2013, 1:15:13 PM10/26/13
to tiddl...@googlegroups.com
Hello,

I'm using TW 2.8.1 with FireFox 24.0.

I've been getting the following error message when exiting a tiddler (auto save = on):

[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]

This locks-up my TW and when I close it and re-open, I've lost the new contents of the tiddler.

I've found a very rough work-around that seems to work.

1) Copy another TW (e.g empty.html) into the same directory
2) Open it and edit a tiddler (no need to change anything in it) and close it
3) Now try and exit the tiddler on the original "locked" TW

This works for me.
Sorry if this isn't news, but I didn't find it when I searched the group.

If any developers read this, I don't think I had this issue before I installed (and then promptly uninstalled) Chrome. Could be a coincidence, due to some plugin or other too.
I don't get this message every time I edit a tiddler, but I haven't yet noticed what does trigger the error.

Anyway, if someone is having this issue and doesn't want to lose their work, try these steps before you consider follicle deracination.

Thanks,

Bob


Jeremy Ruston

unread,
Oct 27, 2013, 10:24:50 AM10/27/13
to TiddlyWiki
Hi Bob

That's useful thanks. I've not heard of anyone else encountering this issue.  What operating system are you using? Do you get the error on every tiddler?

Best wishes

Jeremy


--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.



--
Jeremy Ruston
mailto:jeremy...@gmail.com

Bob Flandard

unread,
Oct 28, 2013, 4:25:31 PM10/28/13
to tiddl...@googlegroups.com, jeremy...@gmail.com
Hello Jeremy,

I can't use my computer at the moment due to a powercut in last night's wind, so I can't test which tiddler/s causes the error.

I'm using Windows 7 x64.

Many thanks to you and your team of developers for a swish tool.

I'll post again if I establish anything specific.

Best regards,

Bob

Steve Tsai

unread,
Dec 31, 2013, 12:17:04 AM12/31/13
to tiddl...@googlegroups.com, jeremy...@gmail.com
I got the same following error message in both 2.8.1 and TW5.0.5 beta. My firefox is version 26.

[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]

And Bob's work-around did work on my computer. So now I can start to enjoy version 2.8.1 and 5.0.5  beta.

Best Regards,
Steve Tsai

Bob Flandard於 2013年10月29日星期二UTC+8上午4時25分31秒寫道:

Jeremy Ruston

unread,
Jan 1, 2014, 3:09:36 PM1/1/14
to Steve Tsai, TiddlyWiki
Hi Steve

That's interesting. Can you reliably reproduce the error? The error message suggests that the attempt to save the file is failing because it is locked; that would typically mean that another process has write access to the file. The suspects might be:

* Another Firefox extension - it's worth trying again with all other extensions disabled
* File sync apps like Dropbox/Box/GoogleDrive etc 
* Antivirus software

Best wishes

Jeremy

Stephan Hradek

unread,
Jan 7, 2014, 7:16:57 AM1/7/14
to tiddl...@googlegroups.com, Steve Tsai, jeremy...@gmail.com
This happens to me too from time to time.

Jeremy Ruston

unread,
Jan 7, 2014, 7:18:40 AM1/7/14
to Stephan Hradek, TiddlyWiki, Steve Tsai
On Tue, Jan 7, 2014 at 12:16 PM, Stephan Hradek <stephan...@gmail.com> wrote:
This happens to me too from time to time.

That's helpful, but I really need to be able to reproduce the problem in order to debug it -- I'd much appreciate any help with reproducing it,

Best wishes

Jeremy

Stephan Hradek

unread,
Jan 7, 2014, 7:30:37 AM1/7/14
to tiddl...@googlegroups.com, Stephan Hradek, Steve Tsai, jeremy...@gmail.com
As soon as it happens again, I will try to reproduce. At this very moment it seems it happens after a firefox crash. I had my local TW open when FF crashed. The next save attempt after reopening produced the error.

Stephan Hradek

unread,
Jan 7, 2014, 7:36:24 AM1/7/14
to tiddl...@googlegroups.com


Am Samstag, 26. Oktober 2013 19:15:13 UTC+2 schrieb Bob Flandard:
I've found a very rough work-around that seems to work.

1) Copy another TW (e.g empty.html) into the same directory
2) Open it and edit a tiddler (no need to change anything in it) and close it
3) Now try and exit the tiddler on the original "locked" TW

I get this error also some times. My workaround:
1) In the filesystem, rename the wiki file
2) save
 

Leo Staley

unread,
Jan 7, 2014, 8:04:23 AM1/7/14
to tiddl...@googlegroups.com
this problem was driving me mad for the past 3 hours.

Frederic ALBOU

unread,
Apr 16, 2014, 3:40:02 AM4/16/14
to tiddl...@googlegroups.com
Hello,
I have the same type of error. And if I copy the file locally instead of leaving it on Dropbox, the error disappears.
Thank you in advance if you find the dropbox error
Best regards
Reply all
Reply to author
Forward
0 new messages