Project

General

Profile

Actions

Bug #16513

closed

JVM GC cannot clean objects in scope in a for { } yield {} even if they are not referenced anymore

Added by Nicolas CHARLES over 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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


Related issues

Related to Rudder - Bug #15675: Leak in Cache of Node Compliance and NodeInfo and perfs improvementReleasedNicolas CHARLESActions
Actions #1

Updated by Nicolas CHARLES over 1 year ago

  • Related to Bug #15675: Leak in Cache of Node Compliance and NodeInfo and perfs improvement added
Actions #2

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from New to In progress
Actions #3

Updated by Nicolas CHARLES over 1 year 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
Actions #4

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from Pending technical review to Pending release
Actions #7

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released

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

Actions

Also available in: Atom PDF