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

Fix the issue of sandbox context not getting garbage collected #1373

Closed
wants to merge 1 commit into from

Conversation

vedkribhu
Copy link
Contributor

@vedkribhu vedkribhu commented Jan 30, 2024

The memory leak surfaced as a result of changes introduced in the following pull request: https://github.com/postmanlabs/postman-runtime/pull/1354/files. Two specific issues led to the memory leak:

  1. We were not removing the Skip request event handler.
  2. The override of context.on resulted in the inability of the garbage collector to handle all handlers attached through context.on.

@codecov-commenter
Copy link

codecov-commenter commented Jan 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1aba274) 79.05% compared to head (d54d2ce) 79.07%.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1373      +/-   ##
===========================================
+ Coverage    79.05%   79.07%   +0.01%     
===========================================
  Files           45       45              
  Lines         3357     3360       +3     
  Branches       964      964              
===========================================
+ Hits          2654     2657       +3     
  Misses         703      703              
Flag Coverage Δ
integration 70.47% <100.00%> (+0.02%) ⬆️
legacy 46.07% <100.00%> (+0.04%) ⬆️
unit 41.87% <25.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@vedkribhu vedkribhu force-pushed the fix/memory-leak branch 2 times, most recently from bc744ab to e1c8aa3 Compare January 30, 2024 14:16
- execution.result and execution.skipRequest listeners
          were not getting garbage collected
@codenirvana codenirvana closed this Feb 1, 2024
@codenirvana codenirvana deleted the fix/memory-leak branch February 1, 2024 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants