You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running test scripts for long time, Selenium UI starts lagging and eventually can freeze. Logger doesn't catch up with printing logs in console and is pausing logs printing when actual pause is triggered.
When having a lot of "Run" commands used for long time one in another (nested), IDE gets overloaded and stops responding and UI elements disappear, just blank screen stays.
To Reproduce
Use some test script which has many times repeating (would be also good to use long) cycle and many "Run" commands, in cycle itself, which run other scripts, would be better if those scripts also would be running other scripts.
Expected behavior
UI shouldn't freeze and IDE logs should be printed at the moment when commands are triggered.
IDE shouldn't be overloaded and crash while using "Run" commands.
Project file reproducing this issue (highly encouraged)
馃悰 Bug Report
When running test scripts for long time, Selenium UI starts lagging and eventually can freeze. Logger doesn't catch up with printing logs in console and is pausing logs printing when actual pause is triggered.
When having a lot of "Run" commands used for long time one in another (nested), IDE gets overloaded and stops responding and UI elements disappear, just blank screen stays.
To Reproduce
Use some test script which has many times repeating (would be also good to use long) cycle and many "Run" commands, in cycle itself, which run other scripts, would be better if those scripts also would be running other scripts.
Expected behavior
Project file reproducing this issue (highly encouraged)
Link for script which may help reproduce 1st issue: ((https://github.com/SeleniumHQ/selenium-ide/files/14024390/dummy.tests.json))
Environment
OS: Windows 10 OS
Selenium IDE Version: 4.0.1-alpha.98 (also appeared with lower versions)
Related issue
#1763
The text was updated successfully, but these errors were encountered: