1316813 - Marionette hangs on GET request

Status: RESOLVED WORKSFORME

(Remote Protocol :: Marionette, defect)

Description

[eportfel]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20161019084923

Steps to reproduce:

I use selenium webdriver with marionette in java.
The page is online banking service with logged user so it cannot be reproduced.


Actual results:

The code worked with Firefox 46 and earlier without marionette.
After moving to Firefox 49 branch, webdriver 3 and marionette it works ok for few first pages than hangs on GET request. The web page loads fine and completly and I have no idea why the proces does not return from GET request. It hangs without any info.


Expected results:

The page should load.

Now I don't know how to debug it further. For instance I do not know how to force marionette to log on DEBUG level (it is set onto INFO level). What to do next.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Can you please tell us more about this test and which pages it accesses? This would be important. Thanks.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Maybe this is a dupe of bug 1314594.

Comment 3

[eportfel]

The page is https://online.mbank.pl you cannot reproduce it as it requires logged on account.

I don't think this is a dupe of mentioned issue, as this is on Firefox and about:blank is not opened at the time of the problem.

For now I found a turnaround just by using Firefox 46.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Can you please attach a full log for when this happens with webdriver and Firefox 49? We would need this for further investigation. Thanks.

Comment 5

[eportfel]

With standard level INFO there is nothing reported in log in the time when it hangs.

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I think we would need at least DEBUG level.

Comment 7

[eportfel]

Please read my first post. I don't know how to change debugging level. Is there any tutorial on this?

Comment 8

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Andreas, can you pleas help out?

Comment 9

[Andreas Tolfsen ❲:ato❳]

Please see the geckodriver README on how to enable trace-level verbose logs: https://github.com/mozilla/geckodriver#firefox-capabilities

Comment 10

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Reporter, please have a look at my blog post which shows an example test written for Selenium:
https://www.hskupin.info/2017/01/23/using-selenium-and-webdriver-to-interact-with-insecure-ssl-pages-in-firefox/

With the link Andreas gave you, only the logging option would have to be added to the capabilities:

capabilities.update({'moz:firefoxOptions': {"log": {"level": "trace"}}})

It would be great if you can give us the information. Thanks.

Comment 11

[Andreas Tolfsen ❲:ato❳]

Resolving this until enough information has been added that we can reproduce it.  I’m most willing to re-open this.

Comment 12

[eportfel]

I tried it again with new versions (Firefox 57.0.2, Selenium Java 3.8.1 and newest geckodriver.exe) and the problem disappeared. For me the status of the issue can be changed to FIXED. Thank you.