We just deployed selenium server 2.0b3 (upgraded from 1.0.3). It looks like there are some fairly serious memory leaks - OutOfMemory exception thrown during runs longer than 30 minutes long.
Is there any straight forward workaround for dealing with the memory leaks in the 2.0b3 selenium server?
I was hoping to get the 2.0b3 source, apply the assorted patches submitted thus far and use this. However, when I pull this:
svn checkout http://selenium.googlecode.com/svn/tags/selenium-2.0-beta-3/ selenium-2.0-beta-3
and build with
./go clean release
The resulting binaries don't appear to have the DefaultSelenium.class. Not sure what is going on here...
Alternately, I thought maybe we will just start working with the latest release candidate. However, looks like the DefaultSelenium.class is not here either.
Do I need to upgrade the client code to use WebDriver? I thought things were suppose to be backwards compatible.
Suggestions?