-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Memory Leak from Taskworker #4265
Copy link
Copy link
Open
Labels
Self-hosted: Next ReleaseUsed to track issues and pull requests (PRs) that should be fixed in the next release schedule.Used to track issues and pull requests (PRs) that should be fixed in the next release schedule.
Description
Metadata
Metadata
Assignees
Labels
Self-hosted: Next ReleaseUsed to track issues and pull requests (PRs) that should be fixed in the next release schedule.Used to track issues and pull requests (PRs) that should be fixed in the next release schedule.
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
No status
Status
Waiting for: Product Owner
Self-Hosted Version
26.3.1
CPU Architecture
x86_x64
Docker Version
29.1.4
Docker Compose Version
5.0.1
Machine Specification
Installation Type
Fresh Install
Steps to Reproduce
When using Sentry Self Hosted & leaving it on for a while, the memory usage for the Taskworkers keep increasing. I've setup a limit, to ensure once it reaches a certain amount of leakage it reboots due to OOM Limit.
Still, this shouldn't occur.
Expected Result
The Taskworkers not to leak memory
Actual Result
The Taskworkers leak Memory
Event ID
No response