[jboss-jira] [JBoss JIRA] (WFLY-12330) Jandex index retention on Weld

Jandex index retention on Weld ------------------------------ Key: WFLY-12330 URL: https://issues.jboss.org/browse/WFLY-12330 Project: WildFly Issue Type: Bug Components: CDI / Weld Affects Versions: 17.0.1.Final Environment: Red Hat JBoss Enterprise Application Platform 7.2 CP 2 Reporter: Teresa Miyar Gil Assignee: Teresa Miyar Gil Priority: Major After deploying a huge amount of Java application in a JBoss EAP environment, it looks like a lot of Jandex index are retained in heap: {noformat} Class Name | Objects | Shallow Heap | Retained Heap --------------------------------------------------------------------------------------------------- java.lang.Object[] | 1,460,530 | 85.52 MB | >= 622.78 MB java.util.ArrayList | 939,474 | 21.50 MB | >= 533.32 MB org.jboss.jandex.Index | 435 | 13.59 KB | >= 460.42 MB org.jboss.as.server.deployment.annotation.CompositeIndex| 224 | 3.50 KB | >= 458.73 MB java.util.HashMap | 1,143,351 | 52.34 MB | >= 405.49 MB java.util.HashMap$Node[] | 897,613 | 89.82 MB | >= 395.81 MB java.util.HashMap$Node | 4,110,870 | 125.45 MB | >= 317.86 MB org.jboss.jandex.ClassInfo | 491,618 | 22.50 MB | >= 301.04 MB --------------------------------------------------------------------------------------------------- {noformat} Test done with heap defined with 4Gb, started nicely with about ~150 applications and slowly increased it until about 200. Less heap then that leads into OOME. Heap: Size: 1.4 GB Classes: 49.5k Objects: 38.6m Class Loader: 1.8 + 900mb ready for GC. The same behavior is not seen in EAP 6.4.21 and all those 200 can be easily deployed within 1 GB heap size.