Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a new marker to check for memory leaks #52

Merged
merged 5 commits into from
Aug 23, 2023

Commits on Aug 16, 2023

  1. Add a new marker to check for memory leaks

    Users have indicated that it will be very useful if the plugin exposes a
    way to detect memory leaks in tests. This is possible, but is a bit
    tricky as the interpreter can allocate memory for internal caches, as
    well as user functions.
    
    To make this more reliable, the new marker will take two parameters:
    
    * The limit of memory per location to consider an allocation. If the
      memory leaked by any allocation location in the test is higher than
      this value, the test will fail.
    
    * An optional callable function that can be used to filter out
      locations. This will allow users to remove false positives.
    
    Signed-off-by: Pablo Galindo <[email protected]>
    pablogsal committed Aug 16, 2023
    Configuration menu
    Copy the full SHA
    8aea9b0 View commit details
    Browse the repository at this point in the history

Commits on Aug 17, 2023

  1. Configuration menu
    Copy the full SHA
    42495b8 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    b71d68d View commit details
    Browse the repository at this point in the history

Commits on Aug 18, 2023

  1. Configuration menu
    Copy the full SHA
    7705a53 View commit details
    Browse the repository at this point in the history

Commits on Aug 22, 2023

  1. Configuration menu
    Copy the full SHA
    8dc0dcf View commit details
    Browse the repository at this point in the history