Weird error

[Alex S. Garcia]

So here's a weird one...

I just did some minor editing to a file (deleted a tiddler and a reference to
it in another) and I hit 'save changes'... and I got this:

[Exception... "Component returned failure code: 0x8007000e
(NS_ERROR_OUT_OF_MEMORY) [nsIScriptableUnicodeConverter.ConvertFromUnicode]"
nsresult: "0x8007000e (NS_ERROR_OUT_OF_MEMORY)" location: "JS frame ::
file:///path/to/my/file.html :: mozConvertUnicodeToUTF8 :: line 203104" data:
no]

First time I see this.

I noticed the 'out of memory' bit, but I have 2 GB left on that partition, so
that can't be it.

Even stranger: I have a bunch of other TW files in the same location, so I
tried to edit and save another one and it worked fine there!

So I closed this tiddly, re-opened it and tried to edit it again... got the
same error!

I should point out that I've been able to work and edit on that file without
any issues for months, and now all of a sudden this??

Any ideas, anyone?



Alex.
--
-------------------------------------------------------------------------
http://www.alexsgarcia.com/
http://www.myspace.com/asglyrics
Music Videos : http://mvdbase.com [database]
http://www.freelists.org/list/mv [mailing-list]
-------------------------------------------------------------------------

[PMario]

Hi Alex,

It would be nice to know your OS, Browser + Version, TW Version. Do you use TiddlyFox with FF? How big is your TW - file size.

Did you install any new Browser AddOns or Browser Apps? ... If so just disable them and try again.

-mario

[Alex S. Garcia]

Hi Mario,

> It would be nice to know your OS, Browser + Version, TW Version.

Yeah, sorry, I should have thought to provide that information.

So, let's see... I'm running a linux box (KDE on Mandriva). I typically use
Firefox (an old version, admittedly, 10.0.5, but as I've said other tiddly
files work fine so I'd be surprised if this was the issue).

As for TW, it's a somewhat old version as well (and a modified one). Quoting
from the relevant 'AboutTWW' tiddly:

"Tiddlywiki Write (updated 11-22-10) is an implementation of the Tiddlywiki
concept (version 2.6.1) and is an experiment in mind mapping for writers."

> Do you use
> TiddlyFox with FF? How big is your TW - file size.

I don't use TiddlyFox (first time I even hear about it, heh).

Regarding size, ah, well, that's another thing ;-) The file is fairly large,
7.5 MB.

> Did you install any new Browser AddOns or Browser Apps? ... If so just
> disable them and try again.

No, not that I can think of. And that's perhaps the most puzzling of all :-o

It may be the file size, though, that is causing the problem. The other file I
tested with yesterday was much smaller. I just tried with another large one
(7.9 MB) and the first time I tried to save, nothing happened. The second
time, Firefox crashed.

Then again, I had a lot of tabs open and I've noticed before that FF (this
version anyway) can be a bit unstable with too many open tabs.

Thing is, now that I've restarted FF, I can save again just fine :-o

Very weird.

[PMario]

On Wednesday, April 29, 2015 at 10:50:23 AM UTC+2, Alex S. Garcia wrote:

Thing is, now that I've restarted FF, I can save again just fine :-o

good :)

----------- some side notes.

Older versions of firefox had a reported problem with memory leaks. .. a long time ago. They worked hard to find and fix them ...
There is a special URL that you can try:    about:memory

If this URL doesn't show anything with your browser, it is a version that may still have these problems. eg: with many tabs open and FF running for a very long time. ....

see: https://blog.mozilla.org/futurereleases/2012/08/28/more-on-firefox-memory-improvements/
and https://developer.mozilla.org/en-US/docs/Mozilla/Performance/about:memory

have fun!
mario

[Alex S. Garcia]

Still wondering what caused this, though.

Are there known issues linked to file size? If so, this could happen again and
even possibly get worse, so it'd be good to know...

How large can I allow a TW to grow?



Alex.

On Wednesday 29 April 2015, PMario wrote:
> On Wednesday, April 29, 2015 at 10:50:23 AM UTC+2, Alex S. Garcia wrote:
> > Thing is, now that I've restarted FF, I can save again just fine :-o
>
> good :)
>
> ----------- some side notes.
>
> Older versions of firefox had a reported problem with memory leaks. .. a
> long time ago. They worked hard to find and fix them ...
> There is a special URL that you can try: about:memory
>

> If this URL doesn't show anything with your browser, it may be a version

> that may still have these problems. eg: with many tabs open and FF running
> for a very long time. ....
>
> see:
> https://blog.mozilla.org/futurereleases/2012/08/28/more-on-firefox-memory-i

> mprovements/ and

> https://developer.mozilla.org/en-US/docs/Mozilla/Performance/about:memory
>
> have fun!
> mario

[PMario]

On Wednesday, April 29, 2015 at 10:47:18 PM UTC+2, Alex S. Garcia wrote:

Are there known issues linked to file size? If so, this could happen again and
even possibly get worse, so it'd be good to know...

I was writing about old  FireFox issues. Not about TW problems.
 

How large can I allow a TW to grow?

There have been some tests with big embedded images, where the TW file was 50+MByte. It was slow but worked using latest FF.

I did some tests with 20.000+ tiddlers. File Size 20MB and up. Performance info was with my "old" single core 2 threaded Notebook.

see:

[1] 20'000 tiddlers
https://groups.google.com/forum/#!msg/tiddlywiki/E9DMg4ZTccw/P1qjS_-HOjAJ

[2] 100'000 tiddlers
https://groups.google.com/d/msg/tiddlywiki/sH4EZukozdM/PM4P3Iy_iWoJ

I did the [1] test just now with 40.000 tiddlers and with my actual computer it saves just fine. 46MB file size. It isn't convenient to work with, but it shouldn't crash the browser.

have fun!
mario

[Alex S. Garcia]

> I did some tests with 20.000+ tiddlers. File Size 20MB and up. Performance
> info was with my "old" single core 2 threaded Notebook.

> [...]

> I did the [1] test just now with 40.000 tiddlers and with my actual
> computer it saves just fine. 46MB file size. It isn't convenient to work
> with, but it shouldn't crash the browser.

Nice!

Very interesting stuff.

Thank you for those links. And for your assistance ;-)



Alex.