Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New async memo reveals a held signal update early

Open
  • Is something wrong?
#3,800 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, typescript
Domain
frontend

Research direction

Start by reading the async memo and scheduled render-effect behavior in the repository, then compare the issue’s reproduction with the earlier report #3408. The linked playground reproduces the early reveal; no source file or test is named, so locate or add focused coverage for synchronous versus asynchronous first results and the explicit flush. Done when the new observer remains held until the slow derivation settles.

Written by the indexing model from the issue text.

Description

Describe the bug

A newly created async memo reads an update that is still held by an existing async derivation, then notifies a scheduled render effect before that update is revealed. The existing scheduled render effect still last reported count = 1, slow = 1, while the new one reports 2.

The same newly created memo stays held when its first result is synchronous. Returning Promise.resolve(count()) instead makes it reveal early.

Your Example Website or App

https://s.olid.uk/id/22KYZfNOSnqqlHlUzL1MqQ

Steps to Reproduce the Bug or Issue
  1. Open the playground console and press Build (or reload).
  2. After about one second, observe parent 1 1.
  3. About 100ms later, observe child 2 while the parent is still held at 1 1.
  4. Roughly one second after that, the slow derivation settles and the parent finally reports parent 2 2.
Expected behavior

The new scheduled render observer should stay held until the input update can be revealed with its slow derivation. An asynchronous first result should preserve the inherited hold, just as a synchronous first result does.

Screenshots or Videos

No response

Platform
  • OS: Linux
  • Browser: Chromium 151.0.7922.173
  • Solid: 2.0.0-rc.13 in the playground; also reproduced on upstream next at b0bad02, in development and production.
Additional context

Both render effects use { schedule: true }, so this excludes the immediate mounting-effect path. The repro uses only primitives.

Two controls preserve the hold:

  • Replace Promise.resolve(count()) with count().
  • Remove the explicit flush() before creating the new memo.

The development warnings about unowned effects are expected in this minimal repro.

Related earlier report: #3408. Here the synchronous first result behaves correctly; the asynchronous first result does not.

Dominant language
TypeScript
Stars
36.1k
Forks
1.1k
Avg merge
13h 13m
Merged PRs (30d)
306

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from solidjs/solid

All issues in solidjs/solid

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.