sslSupport causing Memory Leaks

[lukeis]

Originally reported on Google Code with ID 6964

Before filing an issue, please read the page at
http://code.google.com/p/selenium/wiki/SeleniumHelp This contains lot of
information about how best to get help, and tells you what we need to know.

Still here? We know that bugs are frustrating and annoying things. We also
know that you've probably spent ages trying to figure out what's wrong. The
more information you give us now, the more likely it is that we'll be able
to help.

What steps will reproduce the problem?
1. execute a batch file with the following command line "java -Xms1024m -Xmx1024m -jar
C:\Users\Administrator\Documents\selenium-server-standalone-2.39.0.jar -firefoxProfileTemplate
"C:\Users\Administrator\AppData\Roaming\Mozilla\Firefox\Profiles\TestUser" -role node
-hub http://198.101.238.164:4444/grid/register -nodeConfig C:\Users\Administrator\Documents\NodeConfig.json
-log C:\Users\Administrator\Documents\nodeFirefoxLog.log"
2.
3.

What is the expected output? What do you see instead?
Expected:
A command window with the information that the node is registered. No other information
until a test was ran. And no memory leaks.

Actual:
The command window opened, information that node was registered was displayed, then
the path to the jar file appended with "!/sslSupport".
In the Temp/2 directory folders were being created with the names like "seleniumSslSupport8851781337814934225www.HTTP_FORBIDDEN.net".
In the log file there are warnings being reported about invalid lengths for other URLs,
and also bad connections.

Log Snippet:
20:14:28.709 WARN [93] org.openqa.jetty.http.HttpConnection - POST https://sports.bwin.com/en/sports/indexmultileague
HTTP/1.1
java.lang.IllegalArgumentException: Malformed URI 'https://sports.bwin.com:443https://sports.bwin.com/en/sports/indexmultileague'
: java.lang.NumberFormatException: 443https:
    at org.openqa.jetty.util.URI.setURI(URI.java:247)
    at org.openqa.jetty.util.URI.<init>(URI.java:86)
    at org.openqa.selenium.server.ProxyHandler$SslRelay.customizeRequest(ProxyHandler.java:769)
    at org.openqa.jetty.http.SocketListener.customizeRequest(SocketListener.java:275)
    at org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:922)
    at org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
    at org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243)
    at org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:358)
    at org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:537)
20:14:42.297 WARN [109] org.openqa.jetty.http.HttpConnection - Invalid length: Content-Length=91787
written=24771 for http://mail.126.com/?rands=16615230.
Memory jumps from 67,000K to over 300,000K on the first SockectLinster call.
Selenium errors out in minutes to OutofMemory exceptions.

This all before a single test is running.

Selenium version: 2.39.0
OS: Windows Winodws 2008 R2 (Cloud Server)
Browser: Firefox
Browser version: 27.0

Please provide any additional information below. A sample reduced test
case, or a public URL that demonstrates the problem will intrigue our merry
band of Open Source developers far more than nothing at all: they'll be far
more likely to look at your problem if you make it easy for them!

Here is the node configuration file:
{
  "capabilities":
      [
        {
          "browserName": "firefox",
         "maxInstances": 5,
          "platform": WINDOWS,
       },
       ],
  "configuration":
  {
    "maxSession": 5,
    "port": 5555,
    "host": ip,
    "register": true,
    "registerCycle": 5000,
    "hubPort": 4444
  }
}

I am running the exact same version on another server for chrome without any issues.

Reported by wbrothers63 on 2014-02-07 12:25:34

[lukeis]

Your description is incomplete. You told how to run the hub. But it is not clear which
programs sends a request to https://sports.bwin.com/en/sports/indexmultileague before
you start the very first test.

Reported by barancev on 2014-02-08 20:10:35

• Status changed: NeedsClarification

[lukeis]

Closing the issue due to inactivity

Reported by barancev on 2014-03-12 09:30:35

• Status changed: Invalid
• Labels removed: Status-Untriaged

[lukeis]

Reported by luke.semerau on 2015-09-17 18:22:06

• Labels added: Restrict-AddIssueComment-Commit