futureporn
/
pm
1
1
Fork 0
Code Issues 72 Pull Requests Packages Projects Releases Wiki Activity

futureporn-qa has a memory leak #71

New Issue
Closed
opened 2023-10-09 18:58:38 +00:00 by CJ_Clippy · 0 comments
CJ_Clippy commented 2023-10-09 18:58:38 +00:00
Owner
Copy Link

Discovered via Netdata cloud, high memory utilization scenario occured due to futureporn-qa.worker.1 taking >= 1.9GB of memory. I assume this is what was previously causing outages on replicator.

Discovered via Netdata cloud, high memory utilization scenario occured due to futureporn-qa.worker.1 taking >= 1.9GB of memory. I assume this is what was previously causing outages on replicator.
CJ_Clippy added the
bug
 label 2023-10-09 18:58:41 +00:00
CJ_Clippy added this to the Nov 2023 Sprint project 2023-11-01 10:31:28 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
Labels
Clear labels   
bug

Something is not working

  
Chore

Implements no feature, but needs doing to keep things tidy.

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
Goal

Issues displayed on the website

  
help wanted

Need some help

  
invalid

Something is wrong

  
Mission

Overarching goals that drive what we do

  
process

routine tasks which must be done a specific way

  
question

More information is needed

  
Sprint

A short duration todo list, agile style

  
wontfix

This won't be fixed

No Label
bug
Chore
duplicate
enhancement
Goal
help wanted
invalid
Mission
process
question
Sprint
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Nov 2023 Sprint
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: futureporn/pm#71
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?