Skip to content
This repository has been archived by the owner on Mar 12, 2018. It is now read-only.

DocPad 6.55.3 — Failing with 'process out of memory' #28

Closed
cathybrode opened this issue Nov 27, 2013 · 11 comments
Closed

DocPad 6.55.3 — Failing with 'process out of memory' #28

cathybrode opened this issue Nov 27, 2013 · 11 comments
Labels

Comments

@cathybrode
Copy link
Contributor

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

Performing generate: Write the database cache at 8/9 89%
 ===========================================---
---FATAL ERROR: JS Allocation failed - process out of memory
An error occured within the child DocPad instance: exited with a non-zero status code
@mikeumus
Copy link
Member

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?

@cathybrode
Copy link
Contributor Author

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?


Reply to this email directly or view it on GitHubhttps://github.com//issues/28#issuecomment-29421072.

@mikeumus
Copy link
Member

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.

@mikeumus
Copy link
Member

Upgrading to DocPad 6.55.8 (latest at the time of this comment), is producing the nextTick error again:

@mikeumus
Copy link
Member

Patched as per: afcb2e4

  • Locally, make sure the node_modules/docpad-plugin-related folder is removed.
  • Run docpad clean -> docpad update -> docpad run

@cathybrode
Copy link
Contributor Author

v6.56 is giving out of memory error :(
Performing generate: Write the database cache at 8/9 89% ===========================================------FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory
An error occured within the child DocPad instance: exited with a non-zero status code

@mikeumus
Copy link
Member

mikeumus commented Dec 2, 2013

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

@cathybrode
Copy link
Contributor Author

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

@cathybrode
Copy link
Contributor Author

It is now working correctly with 6.56 on my mac!

@cathybrode
Copy link
Contributor Author

Meant to add an 'however' 173/193 files generated. What about the other 20 it was using?

@cathybrode cathybrode reopened this Dec 2, 2013
@mikeumus
Copy link
Member

mikeumus commented Dec 3, 2013

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 docpad deploy-ghpages --env static command, we see that 100% of the objects were written:

Compressing objects: 100% (250/250), done.
Writing objects: 100% (337/337), 19.38 MiB | 191 KiB/s, done.
Total 337 (delta 133), reused 0 (delta 0)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants