hexo s failed since Hexo 3.2.0

[LouisBarranqueiro]

config

• OS : OS X 10.11.3
• node : 4.4.0
• hexo-cli : 1.0.1
• hexo : 3.2.0

bug stack trace

<--- Last few GCs --->

   25203 ms: Mark-sweep 1397.3 (1457.5) -> 1397.3 (1457.5) MB, 1796.8 / 0 ms [allocation failure] [GC in old space requested].
   27007 ms: Mark-sweep 1397.3 (1457.5) -> 1397.1 (1457.5) MB, 1804.6 / 0 ms [allocation failure] [GC in old space requested].
   28784 ms: Mark-sweep 1397.1 (1457.5) -> 1397.1 (1457.5) MB, 1776.4 / 0 ms [last resort gc].
   30582 ms: Mark-sweep 1397.1 (1457.5) -> 1397.1 (1457.5) MB, 1798.2 / 0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x2afc6adb4629 <JS Object>
    1: write [/Users/louis/hexo-blog/node_modules/hexo/node_modules/warehouse/node_modules/JSONStream/node_modules/jsonparse/jsonparse.js:~80] [pc=0x3bc9585b060d] (this=0x2ba1e5e87549 <a Parser with map 0x2a43f45b47e1>,buffer=0x2da4e9789921 <an Uint8Array with map 0x2a43f45b4ba9>)
    2: /* anonymous */ [/Users/louis/hexo-blog/node_modules/h...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Abort trap: 6

Steps to reproduce the bug

1. Run hexo s
2. Stop process with CTRL + C
3. Run hexo s

It works well with Hexo 3.1.1.

[leesei]

Can you try this?

[leesei]

@LouisBarranqueiro ping
does the solution work?

[LouisBarranqueiro]

Sorry, I forgot to put the answer. No, your solution didn't work. I update node version to 5.7.1.