Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[2.0] Mounting a memo during a held action can crash a render callback

Cerrado
  • ¿Algo no está bien?
#3,802 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, typescript
Área
frontend

Línea de trabajo

Start by reproducing the crash in the linked playground, then trace the Solid 2.0 render callback path for a mounted <Show> child whose memo reads a held signal while another attribute changes. The issue names no source files or tests, so locate the relevant callback and add a regression test for the described timing. Done means the attribute update no longer throws or halts reactivity, and the subtree renders when the action settles.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Describe the bug

While an action holds a signal write, mount a child that creates a memo reading that signal and a div whose attributes read the held signal and a separate signal. Changing the separate signal before the action settles crashes the generated render callback and halts reactivity.

Chromium reports:

TypeError: Cannot destructure property 'e' of 'undefined' as it is undefined.
[REACTIVITY_HALTED] An uncaught error halted the reactive system.

Firefox reports TypeError: (destructured parameter) is undefined.

Your Example Website or App

https://s.olid.uk/id/4hhg1oZMQaasPugrwwLnfA

Steps to Reproduce the Bug or Issue
  1. Open the linked playground.
  2. Click Run once.
  3. The action stages a signal write and waits 2 seconds. After 100 ms, the Show child mounts and creates a memo reading that signal. After another 100 ms, a separate signal changes the div's title.
  4. Observe the TypeError and REACTIVITY_HALTED in the console.
Expected behavior

The pending read may hold the subtree's reveal, but updating another attribute should not invoke its render callback with undefined or halt reactivity. The subtree should render normally when the action settles.

Screenshots or Videos

No response

Platform
  • OS: Linux (browser reproduction)
  • Browser: Chromium 153.0.8010.12; Firefox 155.0
Additional context

Solid experimental preview mizulu/solid2@6f77b1b for solid-js, @solidjs/signals, and @solidjs/web.

The reproduction uses three signals, one action, one Show, and one createMemo. No stores, optimistic state, lists, routing, lazy components, or refresh runtime are involved. It uses ordinary 100 ms delays between updates; no manual flush or microtask scheduling. Tailwind is disabled.

Lenguaje dominante
TypeScript
Estrellas
36.1k
Forks
1.1k
Merge medio
11 h 42 min
PR fusionados (30 d)
326

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de solidjs/solid

Todos los issues de solidjs/solid

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.