Closed kdheepak closed 2 weeks ago
I never encountered this one. Which OS are you ?
It feels this will be hard to reproduce and I would think this is environment dependant. I suspect we need more informations to hope finding what could cause it.
@cscheid @gordonwoodhull does it ring a bell for you such error ?
Thanks
From the paths, I would say it's macOS.
FWIW, I never had a segfault fault in Quarto under any OS.
It is macos. I was hoping the line number could help here. This seems to happen more if I ctrl + c a quarto preview
and run it again immediately.
This is a brand new macOS machine, so I’m not sure if there’s anything particularly special about this environment
I was hoping the line number could help here
This line is the call to deno
command that call the quarto.ts
main file. So possibly something related to Deno itself.
@kdheepak Could you provide more details on your environment? macOS version, how you installed Quarto, etc.
Since you said "brand new macOS machine", I assume you are running on an Apple Silicon CPU thus ARM64.
I see deno segfaults on macos (M3 MacBook Pro) but very rarely (less than 1% of the time, and never twice in a row).
I'm usually rendering and not previewing.
It would be nice to have a consistent repro for this!
I tried this example about 20 times in a row and didn't see it.
@mcanouil we need repro, but this could be hard to have one. I think this is among issue that should stay open to compile further report, even if no repro is provided yet. Just mentioning in case we have a way to tell the bot not to close this one as stale.
Yes, we are on the same page, but worth making it explicit to avoid closing it in 2/3 weeks. 😉
Thank you for using Quarto and reporting an issue!
Unfortunately, this issue is now considered stale because it has been opened since 14 days without providing a "working" reproducible example to help us investigate. If you are still facing the issue, please review the "Bug Reports" guide on how to provide a fully reproducible example as a self-contained Quarto document or a link to a Git repository. Without a reproducible example, it is unlikely that the issue will be addressed.
You can share a Quarto document using the following syntax, i.e., using more backticks than you have in your document (usually four ````
).
````qmd
---
title: "Reproducible Quarto Document"
format: html
---
This is a reproducible Quarto document using `format: html`.
It is written in Markdown and contains embedded R code.
When you run the code, it will produce a plot.
```{r}
plot(cars)
The end.
I haven't seen a segfault since this conversation last month. I was seeing it rarely but regularly before then.
I don't think we have changed Deno version in that time, but I am inclined to think that it was instability on their side which has passed (?)
I'll reopen if I see this again.
Bug description
I'm getting a randomly occurring segfault on an empty revealjs document:
Here's the output I got from the most recent time it happened:
Here's the quarto version number:
Steps to reproduce
quarto create project default
Expected behavior
No response
Actual behavior
No response
Your environment
No response
Quarto check output