https://github.com/nwalters512/sentry-memory-leak-repro

https://github.com/nwalters512/sentry-memory-leak-repro

Last synced: 3 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/nwalters512/sentry-memory-leak-repro
• Owner: nwalters512
• Created: 2024-07-25T15:50:27.000Z (3 months ago)
• Default Branch: main
• Last Pushed: 2024-07-25T16:54:42.000Z (3 months ago)
• Last Synced: 2024-10-10T03:10:51.386Z (27 days ago)
• Language: JavaScript
• Size: 19.5 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# sentry-memory-leak-repro

A reproduction for the Sentry bug described here: https://github.com/getsentry/sentry-javascript/issues/13055

## Steps to Reproduce

1. Clone the reproduction repository

2. Run npm install

3. Run npm run start

4. Run curl http://localhost:3000/ a few times

## Expected Result

I would expect the log from each request to show just a single event processor. This would indicate that event processors aren't leaking between requests and thus that request isolation is working correctly.

## Actual Result

Every time a request comes in, another event processor is added to the existing scope, indicating that the same scope is being shared among all events. In practice, this will lead to a memory leak, since the array of event processors will grow without bounds.