iOS seed is shut down right after bootstatus, so every clone repeats iOS's first-boot work

Abierto
#1,540 2 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
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
devtools, mobile

Línea de trabajo

Start with src/drivers/ios/index.ts and read #makeSeed, #bootAndWait, and #shutdown to trace the seed lifecycle; related issue #1202 may provide context. The issue suggests waiting for the simulator to settle, but leaves the completion signal or configurable delay to decide. Done when seed creation preserves the first-boot work so later clones avoid repeating the reported load spike.

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

Descripción

bug:new
What happened

Every fresh lease of an iPhone Duo simulator (iOS 27.3) spent about 5 minutes in iOS first-boot work
after the clone booted. Poster extensions, BackgroundShortcutRunner, CommCenter and other first-boot
daemons were running, and the host load average reached 200-400 (Apple silicon, 16 GB).

During that window:

  • opening Safari took 35-55 s;
  • the first XCUITest snapshot exceeded a 90 s client timeout.
What you expected

A clone of a ready seed should boot into a settled system.

How to reproduce
  1. Let simlock make a new iOS seed for a model.
  2. Lease that model and watch the host load for the first minutes after boot.
  3. Lease it again: every new lease repeats the spike.
Environment

simlock 0.7.0 (main at ee19e97 has the same code), macOS 27.3 arm64, Xcode 27.3, iOS 27.3 runtime.

Logs and evidence

src/drivers/ios/index.ts #makeSeed runs #bootAndWait (bootstatus) and then #shutdown straight
away. bootstatus returns before iOS finishes its first-boot work, so the seed never stores that work, and
each clone does it again.

The workaround we measured:

  1. Boot the seed once in the sources set.
  2. Wait about 8 minutes, until host load is back near idle (about 2.5).
  3. Launch and quit Safari once.
  4. Shut the seed down. It grew from 2.0 to 2.6 GB.

Cold leases from that seed:

  • opening Safari took 8.6-16.6 s;
  • the first snapshot took 3.9-8.75 s;
  • later snapshots took under 1 s;
  • the first-boot spike was gone.

Suggestion: let the seed settle before #shutdown. Settled could mean simulator CPU low for a while, or
a configurable delay such as drivers.ios.seedSettleMs. It costs minutes once per seed rather than once
per lease. Related: #1202.

Lenguaje dominante
TypeScript
Estrellas
705
Forks
40
Merge medio
12 h 9 min
PR fusionados (30 d)
376

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 callstackincubator/simlock

Todos los issues de callstackincubator/simlock

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.