I thought that running it as node.js eliminated the issue of filesize. The tiddlers are separate files that are loaded when one opens the link, right? Or are all those tiddlers actually opened by the browser in the moment one opens the browser?
Dave On Tue, Jan 28, 2014 at 2:05 PM, Jeremy Ruston <[email protected]>wrote: > Hi Dave > > It's actually not Node.js that's running out of memory here, it's the > browser. It's not normal behaviour, though, and I've not seen anything like > this reported before. It's certainly not something that's associated with > running Node.js. > > You say that you've got 2000 tiddlers in there with many images, perhaps > it's just that you're generating a sufficiently large TW file to confuse > the browser. > > If you save the wiki as a standalone HTML file, how big is it? > > tiddlywiki --rendertiddler $:/core/save/all index.html text/plain > > Another possibility is that you've inadvertently set up an infinite loop - > TW tries to protect you from circular transclusion, but if you somehow > managed it, the symptom would likely be an out of memory error. > > Best wishes > > Jeremy > > > > On Tue, Jan 28, 2014 at 7:00 PM, David Gifford <[email protected]> wrote: > >> This is a pretty important question for me. If I don't get this resolved, >> node.js will not be worth investing my time and effort in. >> >> Dave >> >> >> On Tuesday, January 28, 2014 7:43:52 AM UTC-5, David Gifford wrote: >>> >>> Hi all >>> >>> >>> In node.js, using 5.0.6 beta, Windows 8.0, Firefox, I am starting to get >>> the message below. Not sure what memory it is out of. This is a brand new >>> computer with lots of memory. Tried clearing the browser history, etc, and >>> that hasn't helped. Amazingly, though, the tiddlers did manage to save, >>> despite the error message. Any ideas? I have just over 2000 tiddlers, many >>> of them are image tiddlers. And I tweaked the tiddlerinfo panel so that >>> there is an extra tab that displays the title, tags and text of all >>> tiddlers tagged with that tiddler's title. >>> >>> Here is the text of the error: >>> >>> Internal JavaScript Error >>> Well, this is embarrassing. It is recommended that you restart >>> TiddlyWiki by refreshing your browser >>> uncaught exception: out of memory >>> >> -- >> 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 [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/tiddlywiki. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Jeremy Ruston > mailto:[email protected] > > -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWiki" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywiki/dIrdnKRfmj8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/tiddlywiki. > For more options, visit https://groups.google.com/groups/opt_out. > -- David Gifford Christian Reformed World Missions, Mexico City -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
