forked from imeji-community/imeji-gui-testing
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox memory leak: Firefox crashing in some tests #40
Comments
helkv
added a commit
that referenced
this issue
Mar 11, 2019
- Bug 'Firefox crashing on Jenkins (NoSuchSessionException)' does not appear on qa-imeji - With the fix for ticket #40 Firefox should not crash on dev-imeji anymore
helkv
added a commit
that referenced
this issue
Mar 11, 2019
- Added restartDriver() method, which closes the actual WebDriver (browser) and opens a new WebDriver (browser) instance for the tests - Added getBrwoserType() method - Refactored SeleniumTestSuite class
helkv
added a commit
that referenced
this issue
Mar 11, 2019
- Restart Firefox before each test run of the data driven tests (CreateDefaultStatementPrivate, CreateDefaultStatementTest, CreateNewStatementPrivate, CreateNewStatementTest) - This should fix Bug 'Firefox crashing on Jenkins (NoSuchSessionException)' on dev-imeji
helkv
added a commit
that referenced
this issue
Mar 11, 2019
-> Restarting the webdriver (firefox) before each data driven test leads to Jenkins crashing (Reason unknown) - (Temporarily) Removed Restarting the drive before each data driven test - (Temporarily) Added Implicit Wait again
helkv
added a commit
that referenced
this issue
Mar 12, 2019
-> Restarting the webdriver (firefox) in CreateSubcollectionsTest and the data driven tests should prevent Firefox/Jenkins crashing - Reinsert Restarting the firefox drive before each data driven test - Restarting the firefox drive before CreateSubcollectionsTest
helkv
added a commit
that referenced
this issue
Apr 30, 2019
-> Firefox/Jenkins crashed again because of the firefox memory leak. This time caused by CreateMetadataFacetPrivate. - Add Restarting the firefox drive to: CreateDefaultFacets, CreateDefaultFacetsPrivate, CreateMetadataFacet, CreateMetadataFacetPrivate
helkv
added a commit
that referenced
this issue
May 2, 2019
-> Add Restarting the firefox drive to MetadataSelectedItems to have a additional restart when running all tests -> Running MetadataSelectedItems alone would not lead to a firefox crash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Firefox memory leak:
If there are a lot of actions performed in Firefox without a break, Firefox consumes more and more memory without releasing it. This can lead to a crash of Firefox, if no more memory is available. Firefox releases the memory only after a certain downtime (when no actions are performed in Firefox).
At least the following Firefox versions are affected: 60.0 , 64.0 , ...
Issue for Selenium Tests:
Some Selenium Tests perform a lot of actions in a row without a longer break. These tests will fail if Firefox is used as the executing browser and Firefox crashes because of the described memory leak.
Also see: https://stackoverflow.com/questions/55072731/selenium-using-too-much-ram-with-firefox
Affected Selenium Tests:
Characteristics (Error messages which occur if Firefox crashes):
Workarounds:
driver.quit();
driver = new FirefoxDriver();
Thread.sleep(30000);
The text was updated successfully, but these errors were encountered: