On 10/19/05, Brett Porter <[EMAIL PROTECTED]> wrote: > That's a good point. We will also investigate that avenue. > > Anything in a static var would also be an issue.
Some of our unit tests did have some statics that we'll work on removing, and none of them had instance state that was not nulled out in tearDown. When I exclude the tests with statics from the surefire test suite, leaving 414 tests, the OutOfMemoryError still occurs, so it seems that something else is causing the leak. Note that the unit tests in question are part of the "api-module" project, whereas the OutOfMemoryError occurs during compilation of a subsequent "impl-module" project during the same reactor "install" build. As previously mentioned, skipping the tests causes the problem to go away. However, it is possible that there are multiple leaks (perhaps in some plugins?) and the test suite is just pushing it over the edge to trigger the OutOfMemoryError. Kind Regards, John Fallows. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
