Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Large projects run out of node memory and can't preview or build #748

Open
1 task done
geealbers opened this issue Jun 6, 2023 · 2 comments
Open
1 task done

Large projects run out of node memory and can't preview or build #748

geealbers opened this issue Jun 6, 2023 · 2 comments
Labels
bug Actual behavior does not match expected behavior quire-11ty This is an issue with the quire-11ty package status:backlog Issue is a lower priority but needs to eventually be addressed workaround Issue has a workaround

Comments

@geealbers
Copy link
Member

Before proceeding, check to make sure there isn’t an existing issue for this bug.

  • I have searched the existing issues and determined this is a new bug.

Steps to reproduce

  1. Start with a project that has a lot of Markdown files and/or large images. Like this one with 500 markdown files:
    test-size-limit.zip

  2. Install the project dependencies (npm install) and then run quire preview

Actual behavior

The preview process stops before completing, with this error:

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

Expected behavior

The preview process should carry on and a preview site should display at http://localhost:8080/.

Version numbers

macOS Ventura 13.2.1
Node 18.16.0
Quire CLI 1.0.0-rc.7

What browsers are you seeing the problem on?

No response

Relevant Terminal/Shell output

No response

Supporting Information

See Discussion #742 for some more details.

See also the info we have posted in the Troubleshooting Quire docs to help users increase memory allocated to Node: https://quire.getty.edu/docs-v1/troubleshooting/#working-with-very-large-projects.
@geealbers geealbers added the bug Actual behavior does not match expected behavior label Jun 6, 2023
@Erin-Cecele Erin-Cecele added status:triage needed Issue needs to be triaged by the Quire team. This label is automatically applied to new issues. workaround Issue has a workaround and removed bug Actual behavior does not match expected behavior labels Jun 6, 2023
@Erin-Cecele Erin-Cecele added status:needs discussion Issue needs discussion before being addressed quire-11ty This is an issue with the quire-11ty package bug Actual behavior does not match expected behavior status:backlog Issue is a lower priority but needs to eventually be addressed and removed status:triage needed Issue needs to be triaged by the Quire team. This label is automatically applied to new issues. status:needs discussion Issue needs discussion before being addressed status:backlog Issue is a lower priority but needs to eventually be addressed labels Jun 26, 2023
@hbalenda
Copy link
Contributor

See: https://jira.getty.edu/browse/DEV-15444

@Erin-Cecele Erin-Cecele added status:backlog Issue is a lower priority but needs to eventually be addressed and removed status:needs discussion Issue needs discussion before being addressed labels Jul 12, 2023
@Erin-Cecele
Copy link
Collaborator

@rrolonNelson Thank you for bringing this to our attention in Discussion #742. We have opened this issue and discussed it with the core Quire team. For now, we are backlogging it while we dig deeper into the root cause and potential solutions. It's also worth noting that it seems to be related to other 11ty performance issues, especially this bug (#2226). Please stay tuned for updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Actual behavior does not match expected behavior quire-11ty This is an issue with the quire-11ty package status:backlog Issue is a lower priority but needs to eventually be addressed workaround Issue has a workaround
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@geealbers @hbalenda @Erin-Cecele