CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

43 views
Skip to first unread message

Guillaume Escrivant

unread,
Nov 23, 2018, 6:58:25 PM11/23/18
to TiddlyWikiDev
Hello
I'm a fan user of TW5 on Node.js

I'm one windows with TW5 version 5.1.17

I have a big wiki (230Mo) But the last tiddler i made, i go a node error : CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory with a crash to my node server

And i'm not able to acces my wiki any more.

I've tryed 

  • npm install -g increase-memory-limit
  • increase-memory-limit
adding an option --max-old-space-size=8192 to lauch tiddlywikki

with no success

Does someone have an option ?

Tks for help

Guillaume

Arlen Beiler

unread,
Nov 24, 2018, 1:27:05 AM11/24/18
to tiddly...@googlegroups.com
Can someone please invent an attachments system that can serve files directly from the node data folder! It isn't very hard :)

-Arlen

--
You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/5a0cc15b-62b4-4587-b70b-336097714fc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jeremy Ruston

unread,
Nov 24, 2018, 4:43:19 AM11/24/18
to TiddlyWikiDev
Hi Guillame

As Arlen implies, a useful technique to mitigate large wikis is to move attachments such as images and videos out of the wiki, and address them as files instead of tiddlers.

This is supported in the upcoming 5.1.18 release:


Best wishes

Jeremy

Guillaume Escrivant

unread,
Nov 24, 2018, 6:57:08 AM11/24/18
to TiddlyWikiDev
Tks for the advice
I've move 2 larges png file out of the tiddler, waiting for the 5.1.18 release

my TW5 resume working.

But in the case my TW5 will grow again to the Javascript heap out limitation is there a way to extend it

Tks for your work Jeremy (and all other developer)

Guillaume
Reply all
Reply to author
Forward
0 new messages