-
Notifications
You must be signed in to change notification settings - Fork 59
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
memory leak? #4
Comments
Also run Qt5.2 test suites (java/python) but have not observed such issue yet. |
I'll note that I'm running qt5.2.1 with several patches applied for performance improvements in WebKit. I'm not running stock qt5.2.1...I do have a basic WebView application that I am driving.
WebView application
webdriver.cpp
webview.pro
|
Hi WebDriver should be started in Qt main loop
An example test app is available here https://github.com/cisco-open-source/qtwebdriver/blob/WD_1.X_dev/src/Test/main.cc |
I updated my previous comment and included the code we use to start the web driver. We do start it from the main thread (sorry, I added that in too). Maybe I need to use different options to start the server and in my 'capabilities' set in the test? |
Python test is fine.
|
Have tried with and without OpenGl. I can get the memory issue to happen. I've asked another developer to reproduce my findings, and he also can see the memory leak. We've done research into why there is a memory leak, but have not made headway due to the large WebKit codebase. |
We reproduced the leak, even launching pages without WD. |
Less QEventLoops in widget executors & delay server responses until t…
Is anyone else experience high memory usage and leaks when exercising this code?
I'm using qt5.2.1 and this code in conjunction with a sample python selenium script that loads Yahoo and does a search. If I run this test code a few times, I can see the allocated memory in 'htop' is climbing and not recovering. I have an advanced test suite that can drive the browser to exhaust all available memory. :-(
The text was updated successfully, but these errors were encountered: