Skip to content

mirai session start kills the editor after 180 s while its renderer compiles cold, and says the API did not answer #111

Open

Description

@5hif7y

Related to #109

What happens

mirai session start demo failed on the first try with:

mirai session: the API did not answer in 180 s and the editor was closed (pid …); its log:

The editor was not hung. Its renderer was compiling the pipelines it starts with, from a cold cache.

  • On an RX 580 (amdvlk, Windows 10, i5-7400) that takes 4.5–7 min.
  • The editor is a different executable from the player, so the driver keeps a separate implicit cache for it, and it pays the cold start on its own.
  • A second try with --timeout 900 opened fine.

The code involved:

  • tools/mirai/session.odin:82: the default timeout is 180 s.
  • session_open kills the editor when the timeout runs out (process_kill_pid).
  • The pipeline store saves as it goes (PIPELINE_STORE_SAVE_SHARE), so the kill does not lose everything. A blind retry still pays again for the part that was not saved.

The message reads like a hang, so an agent is likely to retry with the same timeout or report a broken editor.

Expected

session start can tell a renderer that is compiling from one that is stuck. For example:

🤖 Generated with Claude Code

Activity

  1. self-assigned this
    on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions