Skip to content

Call GC before measuring the diff memory in our memory tests #37318

Open

Description

@liyuqian

To reduce false alarms like:

We may still measure the before-GC start/end memory to capture the GC performance. But we need to use after-GC start/end memory to calculate the diff memory.

Activity

  1. added
    c: contributor-productivityTeam-specific productivity, code health, technical debt.
    c: performanceRelates to speed or footprint issues (see "perf:" labels)
    on Jul 31, 2019
  2. liyuqian commented on Jul 31, 2019

    @liyuqian
    ContributorAuthor

    CC @cobblest to see if this could help DevTools on memory

  3. added
    P3Issues that are less important to the Flutter project
    and removed on Jun 28, 2023
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

    P3Issues that are less important to the Flutter projectc: contributor-productivityTeam-specific productivity, code health, technical debt.c: performanceRelates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.perf: memoryPerformance issues related to memoryteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions