-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Out of Memory on 33103 html and with image 671111 regular files #5552
Comments
Wow, got further this time:
Will up to 8192
|
Same error Template render error: (unknown path) |
ANDDDD
Would like to use HEXO and find a solution as I believe in the nodejs path, but seems like when others have hit this wall, they just move to HUGO and it just works. Any help here? |
Ok, surely 32 GB of Ram is enough? haha this must be a deeeper issue...
|
we need separate generator. Like:
This memory heap error because hexo handle all items inside array json database. for now
Rather than process all items in one process, why not get -> process -> save to public folder of each file, it will make hexo memory friendly. |
Wow!
…On October 20, 2024 7:39:11 AM CDT, Dimas Lanjaka ***@***.***> wrote:
for now `marked`, `markdown-it` to process single markdown file, consume 200MB RAM. `hexo` need migration.
--
Reply to this email directly or view it on GitHub:
#5552 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Nice idea. Who are the active devs on this project?
…On October 20, 2024 7:29:12 AM CDT, Dimas Lanjaka ***@***.***> wrote:
we need separate generator. Like:
- `hexo generate tags` only generate tags page
- `hexo generate post` only generate post
- `hexo generate page` only generate page (non post in source/_posts)
- `hexo generate categories` only generate categories page
- `hexo generate assets` only process scss, js, images, non markdown files, post assets into public folder
This memory heap error because hexo handle all items inside array json database.
--
Reply to this email directly or view it on GitHub:
#5552 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Wow! Whonare the developers on this project?
Starting to feel like this project is abandoned
…On October 24, 2024 6:00:17 PM CDT, Dimas Lanjaka ***@***.***> wrote:
Look at my debugger, main out of memory caused while rendering markdown files
![image](https://github.com/user-attachments/assets/8f8df55d-25c7-4534-9620-9b896e36121a)
--
Reply to this email directly or view it on GitHub:
#5552 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
i dont know who the starter dev. but, these ppl still active to review PR @uiolee @SukkaW |
Check List
hexo version
to check)Expected behavior
Run:
or
And the site is generated in record time :)
Actual behavior
Tried #2165 and no luck.
Get out of memory error as such:
Ok, trying on 33103 files and getting fail at 16 gb
in
node_modules/hexo-cli/bin/hexo
Error:
AND, here is the error at 32gb
How to reproduce?
Is the problem still there under
Safe mode
?Yes
Your Node.js & npm version
Your Hexo and Plugin version
Your
package.json
Your site's
_config.yml
(Optional)No response
Others
No response
The text was updated successfully, but these errors were encountered: