After tracing code in Serenity/console-reporter,
I found that ActivityRelatedArtifacts recorded too many Artifact data when continuously running those scenarios, and those data would not be delete after each scenario finished, which probably occupy too much heap and cause allocation fail.
The text was updated successfully, but these errors were encountered:
Yeah, it looks like that bit of code might be using too much memory. That's a nice catch, thanks @wallybb000! Could you please tell me a bit more about what you mean by continuously running scenarios? How exactly do you run them?
wallybb000 commentedApr 28, 2020
I encountered the problem when migrating to 2.0.
After tracing code in Serenity/console-reporter,
I found that ActivityRelatedArtifacts recorded too many Artifact data when continuously running those scenarios, and those data would not be delete after each scenario finished, which probably occupy too much heap and cause allocation fail.
The text was updated successfully, but these errors were encountered: