-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Hexo eats all the memory when generating #3886
Comments
Please try |
Hexo doesn't know what files inside Try to configure |
None of the suggestions made any difference. About 1.5GB of memory is used for generate which is about the size of the directory including all the images. I have my suspicions about the filter https://github.com/hexojs/hexo-filter-responsive-images I think it may be the culprit. I think it may be loading every image into memory to resize them. |
Does disabling the plugin helped? |
I disabled the plugin but it make very little difference. |
I would like to reproduce this. May I know your folder structure, specifically where you put the images ( |
I did not use post_asset_folder. Each post represents a different gallery, which is dynamically built using my script. This just lists the target folder and creates a justified-gallery DIV. I've attached a recursive list of the folder structure. Here is my script. The more images I add the more memory hexo takes when generating. |
This issue has been automatically marked as stale because lack of recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I found that the external_link:
enable: false |
I'm closing this issue due to inactivity. You can join the discussion here: #4922 |
I am building image gallery site. It will have many large images, at the moment with just a small percentage of the images loaded Hexo uses all computer memory when generating the site.
Machine is Linux quad core with 8GB of memory. Hexo eats it all and brings the machine to a standstill due to excessive swapping.
There are 5.7GB of image files. About 1k images.
Looks like Hexo loads everything into memory to generate the site. This is insane!
The text was updated successfully, but these errors were encountered: