Memory consumption in JGiven 0.14.0

[nikowitt]

Hi there,

currently, we're not able to run our builds successfully after updating to JGiven 0.14.0 as they simply stuck (so it's a memory issue). Rolling back to 0.13.0 solves the issue. As I currently cannot provide any specific information, can any experience be shared regarding memory consumption (due to ByteBuddy?)?

Regards,
Niko

[janschaefer]

You are the first one that reports this issue. I will investigate that.

[janschaefer]

Could you tell me which Java version you are using? Have you tried, as a workaround, to inrease the memory?

[nikowitt]

Java/JVM detail version: 1.8.0_72-internal

Regarding memory increase, I'll let you know after I've talked to the admin.

[nikowitt]

Builds are not completed yet, but it seems that increasing the memory helps here.
UPDATE: memory issue still happen, but at a later stage.

[janschaefer]

Ok. Thank you very much for the investigation! Just to narrow down the issue further: are you using Spring?

[nikowitt]

Yes, Spring 4.2/Hibernate 4.3 (I know, we need to update :) ) - but we are using the DataProviderRunner approach using SimpleScenarios and Scenarios.

[janschaefer]

Ok. Then it may also be related to the new Spring implementation.

[janschaefer]

It turns out that ByteBuddy, in contrast to cglib, does not cache generated classes. That most likely causes this issue.