[jbehave-dev] [jira] (JBEHAVE-944) Classloader leak as remove is not called on ThreadLocals in StoryRunner

[Stefan Leonhartsberger (JIRA)]

Title: Message Title

Stefan Leonhartsberger commented on an issue   Re: Classloader leak as remove is not called on ThreadLocals in StoryRunner We can reproduce this issue as well with 3.9.1. Our use case is very simple: We rerun our story a number of times by simply calling: Example.java for(i=0; i < repetitions; i++) { embedder.runStoriesAsPaths(storyPaths); } This ends in a StoryRunner instance per repetition and hence in an OutOfMemory Exception after a lot of repetitions as the reporters which are also retained can keep a lot of recorded data. Moreover NOT calling remove() on the ThreadLocals after the story execution has finished isn't a good practice anyway Add Comment   JBehave / JBEHAVE-944 Classloader leak as remove is not called on ThreadLocals in StoryRunner h4. Overview: StoryRunner uses ThreadLocals however does not call remove() on them after use which leads to a classloader leak in our application which uses a long running thread to load and run stories. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email