fix: cleanup old batches, run their still-current commits

[dummdidumm]

This associates the current batch with the boundary when entering pending mode. That way other async work associated to that boundary also can associate itself with that batch, even if e.g. due to flushing it is no longer the current batch.

This solves a null pointer exception that can occur when the batch is flushed before the next top level await or async derived gets a hold of the current batch, which is null then.

The above is now obsolete, but while investigating this I discovered that we have a memory leak when branches are obsolete/outdated/superseeded. In that case it may happen that their pending count never reaches zero so they're never removed from the batches set. Related to this I discovered that our "commit these DOM changes" logic was flawed: It is possible that an obsolete branch which was neutered would have pending callbacks which we still need to commit. This can happen if e.g. an if block is destroyed by branch A, then branch B superseeds branch A which is then neutered, but the if block tells branch B "nothing changed, I'm already destroyed", never adding a "remove me"-callback to branch B. That only exists in branch A. The fix for both is to compute which branches are now obsolete (they are if all their sources are also covered by the current batch) and to then call all callbacks of effects that don't exist in the current one.

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.
• If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

• Run the tests with pnpm test and lint the project with pnpm lint

[changeset-bot]

🦋 Changeset detected

Latest commit: 28be8c9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
svelte	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Playground

pnpm add https://pkg.pr.new/svelte@16621

[dummdidumm]

Mhm there's a regression with this because e.g. in one case where the batch is switched mid-pending it would be wrong to associate a new-outdated batch the boundary. Mhhhm.

Update: Discovered a memory leak through this: batches that are superseeded are never cleaned up. They're put into the batches set but never cleared from it because their pending count never reaches 0.

[dummdidumm]

Fixed all but one test and resolved the memory leak. The one test that is failing now is actually also failing on main if you run it in the playground, not sure why not in the test.

In the test a router is simulated:

<script lang=ts>
	let route = $state('a');
	let ok = $state(false);

	function goto(r) {
		return Promise.resolve().then(() => {
			route = r;
			throw new Error('nope');
		});
	}
</script>

<h1>{route}</h1>
<button onclick={() => route = 'a'}>a</button>
<button onclick={() => route = 'b'}>b</button>
<button onclick={() => route = 'c'}>c</button>
<button onclick={() => ok = true}>ok</button>

<svelte:boundary>
	{#if route === 'a'}
		<p>a</p>
	{/if}

	{#if route === 'b'}
		{#if ok}
			<p>b</p>
		{:else}
			{await goto('c')}
		{/if}
	{/if}

	{#if route === 'c'}
		<p>c</p>
	{/if}

	{#snippet pending()}
		<p>pending...</p>
	{/snippet}

	{#snippet failed(error, reset)}
		<button onclick={reset}>retry</button>
	{/snippet}
</svelte:boundary>

When you click on b you will go into the else branch, which "redirects" you to route c and throws an error. The redirect spawns a new batch, so the old one is obsolete now. It is also marked as neutered, which means its DOM operation callbacks will no longer be committed. That is a problem though since the new batch is only stating "destroy if block with route b and create route c", not "destroy if block with route a" - because for that batch this has already happened. As a result, <p>a</p> stays around when it shouldn't.

I'm unsure how to fix this. We somehow need to know which of the operations of the obsolete batch should be committed, or somehow make the if block dirty again and somehow bypass pass the "if value hasn't changed do early return" logic.

[dummdidumm]

Found a way to commit the correct callbacks of obsolete branches

[dummdidumm]

this is the only thing in this PR that gives me a bit pause, basically that we have no definite way to know which batch is the latest one for which boundary, this "only" feels like a good enough approximation.

[Rich-Harris]

shouldn't this stuff get GC'd along with the rest of the batch?

[dummdidumm]

as said in the meeting, my hunch is that it's possible for obsolete batches to still be called at some point and then we don't want to rerun anything for them.

[dummdidumm]

added a test that would fail without this logic - outdated batches could resolve when they're already destroyed, and could then wrongfully run stuff. Also helps free up memory for never-resolving promises.