Project

General

Profile

Actions
Copy link

Bug #15646

closed

Huge quantity of memory not released after generation

Added by Nicolas CHARLES about 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
5.0.13
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

at the end of the generation, all nodeconfigurations are kept in memory, while they should be dismissed
in DeploymentService, we return the keyValues of the updatedNodeConfigs - andd it somehow keeps a reference to the map, preventing it to be garbage collected

on large install (3500 nodes with hundred of directives per nodes), it uses 3.5Go

It seems it was introduced in 5.0.9 or 5.0.10

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #15648: ComplianceLevels number keep growing in memoryResolvedActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES about 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions
Copy link
 #2

Updated by Nicolas CHARLES about 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/2443
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.13
Actions
Copy link
 #4

Updated by Nicolas CHARLES about 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #5

Updated by François ARMAND about 5 years ago

This is maybe a Scala bug, tracked here: https://github.com/scala/bug/issues/11727

Actions
Copy link
 #6

Updated by François ARMAND about 5 years ago

  • Subject changed from Memory Leak in Rudder 5.0 to Huge quantity of memory not released after generation
Actions
Copy link
 #7

Updated by François ARMAND about 5 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 5 years ago

  • Name check changed from To do to Reviewed
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 5 years ago

This bug has been fixed in Rudder 5.0.13 which was released today.

Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 5 years ago

  • Related to Bug #15648: ComplianceLevels number keep growing in memory added
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF