-
Notifications
You must be signed in to change notification settings - Fork 313
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
Mermaid diagram to pdf lead to Segmentation fault #11066
Comments
Sorry, it's confusing. What version of Quarto produces the issue? |
The current (yesterday evening) version from the repo (I gave the commit ID). Sorry, it is my first time that I file a bug. |
No reason, to apologise. I only wanted to clarify if the bug was before or after you were using the development version. |
Would you mind trying to remove the unnecessary options?
I cannot reproduce on almost the same apparent setup (I'm on macOS Sequoia though). What version of Chrome (or similar) are you using? |
I get the same result with your example given above. |
Thanks!
Likely a Pandoc/Skylighting update in that regards. |
@lrrichter #10910 has been merged and available in 1.6.15 pre-release. You could use built pre-release to have it working if you don't want to bother with dev version with install from git. This would also make sure that there is no side effect of configuration of the dev version.
The error is not thrown by LaTeX rendering. It seems to be at Quarto level. Let's keep investigating ! Using mermaid for PDF output means that snapshoting using chrome will happen to make a version of the mermaid.js content available to LaTeX for PDF rendering. If you have issue only with files using mermaid cells, then it could be linked to this processing. Is this Segmentation Fault error happening with other type of rendering ? Also can you activate debug logging : https://quarto.org/docs/troubleshooting/#verbose-mode Thank you. |
I have done the following:
Do you want the (now lengthy) full quarto check output? |
Thanks a lot ! It would be really helpful if you could you try 1.6.18 and 1.6.19 ? Can you confirm this is only when having mermaid cell in your document that it fails ? Which would confirm that our processing for snapshoting with chrome could be involved. |
Thanks for the advice. I will give it a try. Only how/where can I get Quarto version 1.6.18 and 1.6.19. I cannot see them on the pre-release builds page. If you could give me the concise git command I would try it. |
All releases are on GitHub: https://github.com/quarto-dev/quarto-cli/releases |
Bug description
Rendering of a Mermaid diagram to pdf leads to a segmentation fault in line 192.
Because of the ANSI color code problem (https://github.com/quarto-dev/quarto-cli/pull/10910/files) I had to use the version directly from the git repo (commit 46cdcc3).
Steps to reproduce
Expected behavior
Render the diagram to pdf
Actual behavior
Rendering to pdf stopped with segmentation fault. Rendering to html works.
quarto render mermaid.qmd --verbose
/usr/local/bin/quarto: Zeile 192: 52556 Segmentation fault: 11 "${QUARTO_DENO}" ${QUARTO_ACTION} ${QUARTO_DENO_OPTIONS} ${QUARTO_DENO_EXTRA_OPTIONS} "${QUARTO_IMPORT_MAP_ARG}" "${QUARTO_TARGET}" "$@"
Your environment
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Datum: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
Betriebssystem: Darwin x64 23.6.0
Quarto check output
The text was updated successfully, but these errors were encountered: