Large number of class loaders created in byte code
Reported by Chris Lee:
Investigating the compiled memory usage for a series of 22 large/complex XSL templates compiled with Saxon EE 18.104.22.168 (bytecode optimization enabled) & cached. A large number of Class Loaders are present in the profile: ‘net.sf.saxon.java.JavaPlatform$1’ – 29,319 of them, for a retained size of ~10.5M (~8% of the total retained memory for stylesheets of ~133M).
Seems like there is one classloader for each generated class (compiled template)?
Bug present in Saxon 9.5 and 9.6.
#3 Updated by O'Neil Delpratt almost 7 years ago
- Status changed from In Progress to Resolved
Bug fixed applied in Saxon 9.5, 9.6 and 9.7.
Memory performance test carried out proved that the new mechanism has given an approximate saving of 25% for the xquery30keywords2 test case which created over 200 class objects in the bytecode generation.
Please register to edit this issue