So the others work just tickety-boo, but FF times out at http://127.0.0.1:8888/blank.html.
FF can connect to the target site.
Tried FF 18 and 18.0.2
I have configured neither %PROFILE% nor %WPTDIR%…
wptdriver 1.0 addon does get loaded.
Any help much appreciated.
;Automatically install and update support software (Flash, Silverlight, etc)
exe=“C:\Program Files (x86)\Google\Chrome\Application\chrome.exe”
options=’–load-extension="%WPTDIR%\extension" --user-data-dir="%PROFILE%" --no-proxy-server’
exe=“C:\Program Files (x86)\Mozilla Firefox\firefox.exe”
options=’-profile “%PROFILE%” -no-remote’
exe=“C:\Program Files (x86)\Safari\Safari.exe”
exe=“C:\Program Files (x86)\Internet Explorer\iexplore.exe”
What happens if you actually watch the test one agent e.g. via RDP?
That’s how I know where it is sticking on localhost/blank.html - and by looking at tools->add ons that the wpt addon has loaded…
Grab an updated agent if you haven’t already: https://sites.google.com/a/webpagetest.org/docs/private-instances#TOC-Updating-Test-Agents
The agent in the 2.9 release broke with Firefox 17 or 18 and I haven’t done a new top-level release yet (2.10 is probably coming next week).
P.S. Just for info, only the repeat view test seems to work - but hey this is more than enough to work with. Just mentioning it. Thanks again.
Hmm, that’s really bizarre because first view is working on the public agents.
@p83822 : I had the same problem, I have downgrade from v19 to v17 fore Firefox.
I am having this issue with the 2.11 agent right now… I can get it to work on a few machines, but one is just sitting on blank.html
I have attached a debug log from the run… any ideas as to why this may be happening, but only on certain machines?
Hmm - looks like it is talking to the agent fine but it never gets to the point where it requests work. Could be a race condition in the firefox extension (believe it attaches to a startup event). I’ll take a look and see if I can make that code more robust and send an updated agent over for testing.
I also opened a bug to track it: https://code.google.com/p/webpagetest/issues/detail?id=149
Looks like I managed to reproduce it on my dev system when I went to try to put in some extra hardening. For some reason Firefox isn’t loading the extension at all and it’s not immediately clear why.
It’s my top priority and I’m holding up the next agent release which has a few other goodies in it until I get it fixed so hopefully I’ll have a good handle on it tomorrow.
Thank you for the quick response on this!
ok, in my case it was because the files under “templates/firefox” were marked as read only. You can try manually clearing the flag on the files or grab the agent update that I just released which automatically clears the read only bit if it is set as it sets up the firefox profile.
Here is how to grab the update: https://sites.google.com/a/webpagetest.org/docs/private-instances#TOC-Updating-Test-Agents
I also added some extra logic to the extension to make it more resilient in case your issue was different but the behavior was identical so I’m cautiously optimistic that it should work now.
Is there any way you could send me a source code patch? Or are these changes reflected in the SVN repository?
I am actually running a slightly modified version of the drivers, I’d like to merge the changes into my own build.
Thank you again for the help!