Skip to content

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program. #55546

Description

@HUAHUAI23

Version

v22.9.0

Platform

ubuntu 22.04

Subsystem

No response

What steps will reproduce the bug?

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.
image
mod is vm.script, I didn't set the execution timeout, if I use await here, he will be stuck here all the time

How often does it reproduce? Is there a required condition?

every time

What is the expected behavior? Why is that the expected behavior?

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.

What do you see instead?

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.

Additional information

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.

Activity

  1. HUAHUAI23 commented on Oct 26, 2024

    @HUAHUAI23
    Author

    The problem I've found is that microtaskMode: 'afterEvaluate', which doesn't seem to be supported above es2016, doesn't support async has to be promise

  2. avivkeller commented on Oct 26, 2024

    @avivkeller
    Member

    Hi! Can you please provide a minimal reproduction?

    Additionally, code snippets are better than screenshots for readability.

  3. added
    vmIssues and PRs related to the vm subsystem.
    on Oct 26, 2024
  4. github-actions commented on Apr 27, 2026

    @github-actions
    Contributor

    This issue has been marked as stale due to 210 days of inactivity.
    It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

  5. added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Apr 27, 2026
  6. github-actions commented on May 27, 2026

    @github-actions
    Contributor

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.vmIssues and PRs related to the vm subsystem.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions