Temp directory filling up

[lukeis]

Originally reported on Google Code with ID 1131

What steps will reproduce the problem?
1. Run a remote webdriver test
2. Close the browser
3. Run another remote webdriver test
4. Repeat steps 1-3

What is the expected output? What do you see instead?

Based on a recent thread within the WebDriver Google Group (https://groups.google.com/d/topic/webdriver/T3Ia1S4HeVQ/discussion),
the expected behavior is that the firefox profile data that is generated and stored
within the following Windows directory on the _remote_ server

C:\Users\qauser\AppData\Local\Temp\

should be deleted when the JVM shuts down. Instead, the directories (similar to "anonymous7193804790597412017webdriver-profile\"
) are not being removed from the file system.


What version of the product are you using? On what operating system?

OS = Windows 7
Selenium = v2a6
Selenium Server = selenium-server-standalone-2.0a6.jar 
Web Browser = Firefox 3.x


Please provide any additional information below.

Some additional information that may be helpful:

(1) We are using a testing framework composed of Cucumber + Cuke4Duke + Selenium
(2) We are running our tests remotely using the selenium-server-standalone-2.0a6.jar.
The server is being started using the following command: "java -jar selenium-server-standalone-2.0a6.jar
-port 3333"
(3) We use a 'TestEnvironment' class to instantiate a static instance of WebDriver
(4) The static instance of WebDriver is launched via a Hooks class method, loadTestEnvironment(),
that integrates with Cucumber's "Before" construct.  Sample code for this looks like

import revv.common.TestEnvironment;
import cuke4duke.annotation.After;
import cuke4duke.annotation.Before;

public class Hooks {

    @Before
    public boolean setupTestEnvironment() {
      return TestEnvironment.loadTestEnvironment();
    }

    @After
    public boolean teardownTestEnvironment() {
      return TestEnvironment.unloadTestEnvironment();
    }
}

(5) The browser is loaded before each and every Cucumber scenario and unloaded (closed)
after each scenario - this may occur between 15 - 20 times during a normal test.

Reported by restagner on 2010-12-21 03:57:41

[lukeis]

This issue ha been fixed post a6

Reported by kristian.rosenvold on 2010-12-21 07:11:27

[lukeis]

This issue ha been fixed post a6

Reported by kristian.rosenvold on 2010-12-21 07:11:27

[lukeis]

Since youre using w7 you'll probably want to use b1, which should be out before your
disks fill up again

Reported by kristian.rosenvold on 2010-12-21 07:16:02

• Status changed: Duplicate

[lukeis]

Since youre using w7 you'll probably want to use b1, which should be out before your
disks fill up again

Reported by kristian.rosenvold on 2010-12-21 07:16:02

• Status changed: Duplicate

[lukeis]

Hello,
 We are still observing this issue. upgraded to the latest RC 2.16.1 and I can see
huge data left in temp folder.
Anything else I need to do to clean up this temp folders by JVM ?

Reported by VGINTU on 2012-01-10 23:27:52

[lukeis]

Hello,
 We are still observing this issue. upgraded to the latest RC 2.16.1 and I can see
huge data left in temp folder.
Anything else I need to do to clean up this temp folders by JVM ?

Reported by VGINTU on 2012-01-10 23:27:52

[lukeis]

Hi, 

I'm running Selenium-server-2.23.1 and after running some tests (WIN7), I see my %TMP%
directory filled up (upto 5GO) of temporary sessions (copies of Firefox profile), screen
dumps, etc...

This prevents me from keeping alive my server : I do need to stop it, launch a manual
cleanup command and lauch it again.

I assume that calling selenium.close should destroy everything that has been created
by the session...

Thanks for your reply (and best... correction)

Regards, Olivier.

Reported by obusnel on 2012-06-21 12:57:49

[lukeis]

Hi, 

I'm running Selenium-server-2.23.1 and after running some tests (WIN7), I see my %TMP%
directory filled up (upto 5GO) of temporary sessions (copies of Firefox profile), screen
dumps, etc...

This prevents me from keeping alive my server : I do need to stop it, launch a manual
cleanup command and lauch it again.

I assume that calling selenium.close should destroy everything that has been created
by the session...

Thanks for your reply (and best... correction)

Regards, Olivier.

Reported by obusnel on 2012-06-21 12:57:49

[lukeis]

Solution : call driver.quit after driver.close...

Reported by obusnel on 2012-06-21 13:03:48

[lukeis]

Solution : call driver.quit after driver.close...

Reported by obusnel on 2012-06-21 13:03:48

[lukeis]

Reported by luke.semerau on 2015-09-17 18:11:48

• Labels added: Restrict-AddIssueComment-Commit

[lukeis]

Reported by luke.semerau on 2015-09-17 18:11:48

• Labels added: Restrict-AddIssueComment-Commit