Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Bug]: Object leak in Tracing #2977

@TomasBernotenas

Description

@TomasBernotenas

Version

1.55.0

Steps to reproduce

Example steps (replace with your own):

  1. Clone my repo at (https://github.com/TomasBernotenas/playwright_tracing_leak)
  2. pip install -r requirements.txt
  3. python memleak_test.py
  4. you should see memory and object count increasing after each loop

if tracing is turned off then the memory stays stable and there are no additional objects created after each loop

Expected behavior

Object count and memory should return to initial after tracing is stopped

Actual behavior

When tracing is stopped callback objects keep accumulating

Additional context

No response

Environment

- Operating System: [Windows 11 10.0.22631]
- CPU: [(8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz]
- Browser: [All, Chromium, Firefox, WebKit]
- Python Version: [3.11.9]

Metadata

Metadata

Assignees

No one assigned

    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