OWASP / OWASP/wrongsecrets

Find and fix memory leak

Open
#389 3 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
HTML
Stars
1.5k
Forks
625
Avg merge
14h 21m
Merged PRs (30d)
44

Description

after running hey twice against /challenge/1 we see that the amount of sessions build up to 400, and memory consumption goes from 200Mb to 277 MB after which, when all sessions are released, we still see 274 MB in use (e.g. 70 MB is not GCed?)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.