BadResource: Bad resource ID crash during book project preview (SassCache stale Deno KV handle)

[Artmann]

Bug description

Running quarto preview on a book project crashes with BadResource: Bad resource ID. The error originates from the Sass cache system backed by Deno KV — SassCache.getFromHash calls kv.get() on a KV handle that has already been closed, so subsequent re-renders of the book's pages fail.

This looks like the same root cause as #13955 (stale SassCache instance with a closed Deno KV handle left in _sassCache), which is closed and marked fixed for milestone v1.9. However I'm still hitting it on Quarto 1.9.38 in a book project, where the crash repeats across multiple chapter/part pages during preview re-render (/recipes/asia/, /recipes/americas/, /recipes/oceania/, …). It may be a regression or a code path the original fix didn't cover (the book config path goes through bookRenderItems / bookProjectConfig / refreshProjectConfig).

Steps to reproduce

1. Create a Quarto book project (project: { type: book }) with multiple parts/chapters and an HTML format using a theme + custom CSS, e.g.:

   _quarto.yml:

   project:
     type: book
     output-dir: _book
   
   book:
     title: "Chicken and Rice"
     author: "Me"
     chapters:
       - index.qmd
       - part: "Asia"
         chapters:
           - recipes/asia/index.qmd
       - part: "Americas"
         chapters:
           - recipes/americas/index.qmd
   
   format:
     html:
       theme: cosmo
       css: styles.css

2. Run quarto preview.

3. Trigger a re-render (edit and save a file, or navigate between pages).

4. Observe the crash.

Actual behavior

The preview crashes with BadResource: Bad resource ID, repeated for several pages.

ERROR: BadResource: Bad resource ID

Stack trace:
    at bookRenderItems (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:152897:11)
    at eventLoopTick (ext:core/01_core.js:179:7)
    at async Object.bookProjectConfig [as config] (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:152769:23)
    at async projectContext (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:92038:28)
    at async refreshProjectConfig (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:161559:15)
    at async file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:161719:9

ERROR: BadResource: Bad resource ID

Stack trace:
    at Kv.get (ext:deno_kv/01_db.ts:57:34)
    at SassCache.getFromHash (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:80007:39)
    at SassCache.getOrSet (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:80071:37)
    at eventLoopTick (ext:core/01_core.js:179:7)
    at async compileSass (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:87418:19)
    at async resolveSassBundles (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:125147:17)
    at async resolveExtras (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:129811:14)
    at async runPandoc (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:129235:20)
    at async renderPandoc (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:130920:24)
    at async Object.onRender (file:///C:/Users/Artga/AppData/Local/Programs/Quarto/bin/quarto.js:153801:34)

The Kv.get / SassCache.getFromHash / SassCache.getOrSet / compileSass / resolveSassBundles chain is identical to #13955.

Expected behavior

Preview re-renders the book without crashing — the Sass cache should not reuse a SassCache instance whose Deno KV handle has been closed.

Your environment

• Quarto version: 1.9.38
• OS: Windows 11 Pro (10.0.26200)
• Project type: book (HTML + EPUB + PDF formats configured; crash occurs during HTML preview)

Related

• BadResource error during preview re-render #13955 — same SassCache / Deno KV BadResource root cause (closed, milestone v1.9). This report is the book-project variant, still reproducing on 1.9.38.

[mcanouil]

@Artmann In the future, we would appreciate if you could tell your LLM to use the issue template when filing bug reports (this is not limited to this repository). Thank you for your understanding.

[mcanouil]

I cannot reproduce the issue based on the provided informations.

Note that it would be best to fully describe the step and to reproduce with a fully reproducible setup such as a book created with quarto create project book.

I did:

1. quarto create project book
2. Added a styles.css empty file with the css key in _quarto.yml
3. Trigger quarto preview from the UI (VSCode) on index.qmd
4. Added {{< lipsum 1 >}} at the bottom of index.qmd
5. Trigger quarto preview from the UI (VSCode) on index.qmd

I did not see any crash under the current development version.

As 1.10 pre-release include several quarto preview fixes (https://github.com/quarto-dev/quarto-cli/blob/v1.10.11/news/changelog-1.10.md), would you mind trying it and/or provide clearer steps to reproduce?

[cderv]

Thanks for the report, and for the detailed analysis — it points at the right path.

This is the same root cause as #13955, on a code path that its fix (#13967) didn't cover.

#13967 stopped the single-file preview path (renderForPreview) from tearing down the project context between re-renders, switching to per-file cache invalidation instead:

quarto-cli/src/command/preview/preview.ts

Lines 465 to 467 in 16257ef

	if (project?.fileInformationCache) {
	project.fileInformationCache.invalidateForFile(file);
	}

Book and website preview don't go through renderForPreview. They go through the project serve/watch path, which still rebuilds the project context on each config refresh by calling project.cleanup():

quarto-cli/src/project/serve/watch.ts

Lines 62 to 66 in 16257ef

	const refreshProjectConfig = async () => {
	project.cleanup();
	project =
	(await projectContext(project.dir, nbContext, renderOptions, false))!;
	};

The underlying defect from #13955 is still there: SassCache.cleanup() closes the Deno KV handle but leaves the stale entry in the _sassCache registry, so a later resolve hands back a SassCache whose KV is already closed — BadResource on kv.get():

quarto-cli/src/core/sass/cache.ts

Lines 146 to 160 in 16257ef

	cleanup(temp: TempContext | undefined) {
	const registerCleanup = temp ? temp.onCleanup : onCleanup;
	const cachePath = this.path;
	registerCleanup(() => {
	log.debug(`SassCache cleanup executing for ${cachePath}`);
	try {
	this.kv.close();
	if (temp) safeRemoveIfExists(this.path);
	} catch (error) {
	log.info(
	`Error occurred during sass cache cleanup for ${this.path}: ${error}`,
	);
	}
	});
	}

So the bookRenderItems / refreshProjectConfig lead is correct.

I haven't reproduced the crash on the current dev build yet. It would help to confirm two things from the reproduction: a multi-chapter book, and the theme + custom CSS combination — that combination pulls in Bootstrap's @imports and routes through the session Sass cache, which is the part that gets closed. That's the setup I'll try.

We could fix this at the cache layer so every render path is safe — have SassCache.cleanup() drop its _sassCache entry when it closes the handle, independent of which path triggered the cleanup. I'll look into it.