New issue
Advanced search Search tips

Issue 821370 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 8
Cc:
jmukthavaram@chromium.org
johnchen@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Automation testing

Reported by agor...@gmail.com, Mar 13 2018 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36

Steps to reproduce the problem:
1. Running a ruby script that uses selenium webdriver
2. when switching to menu frame it shuts the browser down
3. 

What is the expected behavior?
window closes

What went wrong?
i think the frame selection changed

Crashed report ID: no

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? Yes 64

Chrome version: 65.0.3325.146  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

this is testing on our internal sites that we do, and they worked flawlessly before

Comment 1 by agor...@gmail.com, Mar 13 2018 

using Windows 7, Ruby 2.4.2p198, selenium-0.2.11, chrome=65.0.3325.146, chromedriver=2.33.506120, selenium-webdriver-3.8.0

ruby command
@driver.switch_to.frame "menu"

Comment 2 by jmukthavaram@chromium.org, Mar 14 2018

Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback Needs-Triage-M65
Thanks for filing the issue.

Could you please provide us the crash server id from chrome://crashes (same as in attached screenshot) to proceed further.
Serverid.PNG
54.4 KB View Download

Comment 3 by agor...@gmail.com, Mar 14 2018 

I was unable to get The crash logs do to chrome using automation extension. I did update the chromedriver to 2.36 and now it seems that the teats are too fast and crashes do to page not loading fast enough.
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 14 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by jmukthavaram@chromium.org, Mar 15 2018

Components: Tests>WebDriver
Adding 'Tests>WebDriver' component. Could someone from respective team please take a look into this issue & update the thread accordingly.

Thanks..!

Comment 6 by agor...@gmail.com, Mar 15 2018 

An Update, looks like the chrome driver needed to be updated to 2.36 to work with 65. But the other issue is when tests are ran they run to fast, even though there is implicit wait. The browser shuts down and tests fail because the page didn't load yet, and its sporadic, same test will pass if page loads faster

Comment 7 Deleted

Comment 8 by jmukthavaram@chromium.org, Mar 22 2018

Labels: TE-NeedsTraige-help
Seems it is out of scope from TE end as it is chrome driver related issue as per C#6, adding TE-NeedsTraige-help label to move this out of our triaging bucket.

Could someone from dev team please take a look into this issue.
Thanks..!

Comment 9 by johnchen@chromium.org, Jul 1

Cc: johnchen@chromium.org
Labels: Needs-Feedback
There has been various bug fixes related to frame handling in the last few versions of Chrome and ChromeDriver. Could you please try again with the latest versions of both? If the problem persists, please provide repro code and/or version log from ChromeDriver.

Comment 10 by johnchen@chromium.org, Aug 8

Status: WontFix (was: Unconfirmed)
Closing the bug as we're unable to repro it.
►

Sign in to add a comment