-
Notifications
You must be signed in to change notification settings - Fork 1
DocPad 6.55.3 — Failing with 'process out of memory' #28
Comments
Thanks to @Aglezabad - docpad/docpad-plugin-related/issues/5, we know that the "related" plugin is the culprit here. Are we actually using any related posts anymore? |
No we're not. Sent from my iPad On 27 Nov 2013, at 21:20, "Michael Duane Mooring" <[email protected]mailto:[email protected]> wrote: Thanks to @Aglezabadhttps://github.com/Aglezabad - docpad/docpad-plugin-related#5docpad/docpad-plugin-related#5, we know that the "related" plugin is the culprit here. Are we actually using any related posts anymore? — |
Seems this ug has been patched in the "related" plugin but since we're not using it anyways I'm going to remove it from package.json. |
Upgrading to DocPad 6.55.8 (latest at the time of this comment), is producing the nextTick error again: |
Patched as per: afcb2e4
|
v6.56 is giving out of memory error :( |
I was able to get 6.56 running locally and on absdemo.com (if you view the source of absdemo, you'll see the version number there). As per: c2911ef |
I had to go back to 6.54.10 as it wouldn't render 20 files for 6.56. However the fonts on the home page are now not displaying correctly |
It is now working correctly with 6.56 on my mac! |
Meant to add an 'however' 173/193 files generated. What about the other 20 it was using? |
I believe this is just the way DocPad works. As long a your changes are there and everything else is okay, then we should be okay. I just upgraded to DocPad 6.57 and upon doing the
|
Initial docpad update (to v6.55.1) gave:
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral. then got RangeError: Maximum call stack size exceeded.
v6.55.3 was then available. Upgraded to that and now get failure
The text was updated successfully, but these errors were encountered: