Actions
Bug #16513
closed
JVM GC cannot clean objects in scope in a for { } yield {} even if they are not referenced anymore
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
GC cannot garbage collect objects in a for yield, as long as they are in scope
We need to help it by putting them out of scope, or not referencing them anymore, or by returning smaller objects
see https://github.com/Normation/rudder/pull/2648/commits/e916e3ebe2c5d5b8299f2b0953b9739ebbe08f42 - it saves a full GB of memory during policy generation
Updated by Nicolas CHARLES over 4 years ago
- Related to Bug #15675: Leak in Cache of Node Compliance and NodeInfo and perfs improvement added
Updated by Nicolas CHARLES over 4 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES over 4 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/2709
Updated by Nicolas CHARLES over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d441f484295acb7b0f313bd4976053c9cf47c2f4.
Updated by Nicolas CHARLES over 4 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 4 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.16 which was released today.
Actions