Fatal javascript OOM in Ineffective mark-compacts near heap limit

[kris-brown]

I'm not sure what the cause of this new behavior is, but after adding a couple hundred pages to my website (mostly text and quite short) I began getting the below error upon quarto render with both the current release and pre-release versions. StackOverflow says this message is usually associated with a memory leak. After the error I can quarto preview and see the built website, but things like full text search are broken. Is there anything I can check on my end to debug this?

...
748/749] docs/blog/index.qmd
[749/749] index.qmd


<--- Last few GCs --->

[30742:0x128048000]   501878 ms: Mark-Compact 1367.4 (1437.0) -> 1355.3 (1440.7) MB, 1384.1 / 0.0 ms  (average mu = 0.136, current mu = 0.016) allocation failure; scavenge might not succeed
[30742:0x128048000]   503297 ms: Mark-Compact 1372.4 (1442.0) -> 1360.7 (1446.2) MB, 1389.6 / 0.0 ms  (average mu = 0.081, current mu = 0.021) allocation failure; scavenge might not succeed


<--- JS stacktrace --->


#
# Fatal javascript OOM in Ineffective mark-compacts near heap limit
#

/Applications/quarto/bin/quarto: line 158: 30742 Trace/BPT trap: 5       "${QUARTO_DENO}" ${QUARTO_ACTION} ${QUARTO_DENO_OPTIONS} ${QUARTO_DENO_EXTRA_OPTIONS} "${QUARTO_IMPORT_ARGMAP}" "${QUARTO_TARGET}" "$@"

[cscheid]

Thank you for the report! That's pretty clearly a bug on our side. I'm going to open an issue to track.