-
Notifications
You must be signed in to change notification settings - Fork 51
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
Error "Javascript heap out of memory" #83
Comments
@webuilderkrish thanks for reporting this. I can see the value in this. |
if there are custom URLs usually it takes few seconds but for dynamic URL I don't know because I am generating one but its not generating. i did wait for whole night but no sitemap |
Thats not right. How many pages do you have? Is it like 1000+? Also; did you get any errors in the Strapi logs? |
i am working on a e-commerce website where I have like 4 lac merchants and 2 million products but i am was generating pages for only merchants still cannot create sitemap and there is no error on strapi console |
Allright. So that’s interesting. I would like to keep in touch with you as I think you are the first to use this plugin with that many URLs. Let’s see how that works out. For the current issue; |
Sure I would be in touch with you. |
Allright, thanks! And can you confirm if the sitemap file isn't silently written? |
yes i did check that it is showing old XML which i created with custom urls |
Well, then I'm fresh out of idea's. I feel like there should be some kind of error, somewehere. |
I am seeing no error in the console or on the browser console. how can i find out the error |
Can you confirm (in browser network tab) that the /sitemap call finishes when you click generate? The sitemap is also generated when you update a page of the collection type you added to the sitemap. |
yes, the sitemap call is getting fired but no response is generating. and when I am updating the entity it sends http://localhost:1337/sitemap/settings/ request |
Hi @webuilderkrish Wanted to quickly follow up on this. So the logical next step would be to do some debugging in the source code. As you mentioned the You could alter that file in your project (node_modules/strapi-plugin-sitemap/server/services/core.js) and put some Hopefully that will give us a bit more context as to what might be going on here. |
Okay I will debug the code and let you know |
hi @boazpoolman I did debug all code I am getting the below error and my server is restarting. |
So a Also I see the log BTW: were you able to pin-point the exact location in the Thanks for investing your time in this 🚀 |
Hi @boazpoolman and about error I think i am getting this error in below code at core,js in services in
thanks.. |
Hey @webuilderkrish I feel like you are fetching more records then you think. As your log from the error screenshot stated For now I can ask you to try the beta version of the plugin. In the beta version the plugin will create a paginated sitemap index of sitemaps containing more then 45.000 records. It’s worth a try. You can install beta like this |
thanks for the update i will use the beta version and let you know the response |
Hi, |
Allright. Thanks for trying at least. All I can do for you now is create a test Strapi app with 500k records and trying to add them to the sitemap, hoping I will get the same error as you so I can do some debugging. Sadly I don’t have time for that anytime soon. So until then I can only encourage you to debug the plugin yourself. Try to optimize the code so you won’t get this error. Sorry I can’t do more for you at this time. |
Thanks for the support I will debug the code and try to find the solution thanks for your time. but please try to fix this bug as you get the time. Thanks for the support... |
I will, once I have the time. If you make any progress on this feel free to reach out! Btw; for future reference; do you have localizations enabled in your Strapi app? |
Okay i will reach out when i will find something |
Hey @webuilderkrish Allright, this is allready more verbose. Not sure if it fixes your issue. |
Performance fixes have been made in version 3.0.0 of the Sitemap plugin. From now on, by default, the sitemap will be generated through CRON, not through lifecycles. That means a lot less sitemap generations. Apart from that tons of small optimisations have been made to make the plugin perform better with large URL sets. |
Bug report
Describe the bug
can't see any notification of sitemap is generating when pressing the button there is no info that how much time it will take or its generating the sitemap
Steps to reproduce the behavior
Expected behavior
It should show that sitemap is generating
System
The text was updated successfully, but these errors were encountered: