Firefox won't start on any port

[vladsoroceanu]

Hi,

I'm trying to lunch the test with -b firefox after install and it says that port 9006 is in use. I tried changing it to 9002, still in use and after using currPorts I can see that those ports are actually not in use.

[vladsoroceanu]

Hi,

I've tracked the error inside portscanner.js and it times out after 400ms. If I increase to 1500ms it works to open the browser and the page, although it shoots a connect ECONNREFUSED errror, but then it crashes in marrionette.js at line 205 saying that the Object true doesn't have method substring.

I didn't know where to go any further from there, because I don't know where those objects come from.

Here are my stats:

dalekjs cli tools: 0.0.4
dalek js local: 0.0.8
Windows 7 64 bit (although when running a test dalekjs says it's windows 7 32 bit)
Firefox installed version: 28.0

Hope this helps!

[asciidisco]

Hi Vairend,

thanks for the report. I will set up a Windows VM (seems that Mac & Linux are ok) & try to reproduce/debug the behaviour.

[SiriusDG]

I am seeing this same issue... was a fix ever created? Thanx!

David

[jayzelenkov]

same here. Win7 64-bit. Firefox 29. Changing ports for Firefox in Dalekfile didn't help. Using port range also didn't fix the problem.

Firefox Beta and Aurora have the same behavior

[SiriusDG]

Turns out this is a timing issue. Go into the Firefox folder and find the config file, change the port timeout to a really high number... I believe I used 4 seconds. Fixed it instantly.

[jayzelenkov]

---

@SiriusDG could you please be a little more specific? What is the name of the config file and which setting should be changed?

[SiriusDG]

I can later, at work right now, this is on my personal machine. Give me a
day. ;)

On Tue, May 13, 2014 at 10:03 AM, Jev Zelenkov notifications@github.comwrote:

@SiriusDG https://github.com/SiriusDG could you please be a little more
specific? What is the name of the config file and which setting should be
changed?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-42958713
.

[KevinSheedy]

I hit the same issue too and the hack above seems to work:
my_project\node_modules\dalek-browser-firefox\node_modules\portscanner\lib\portscanner.js:66

var timeout = options.timeout || 400

Changed to:

var timeout = options.timeout || 4000

I think this works as a quick hack but a proper solution is still required.

[adrianmiu]

I also confirm it's not working. Ubuntu 14.04, Firefox 30.0, Dalek CLI 0.0.4, Dalek 0.0.8

[omarlopesino]

I have the same error using Windows 7 and firefox (versions 29 and 30).
I tried to do what @KevinSheedy said, and the navigator it's opened one second and then is closed.
The error I received is '>> ERROR: Error: not running'.

[asciidisco]

I recently was able to spend some thoughts on this. The problem is, is that the Mozilla developers change the marionette API nearly with every build (which isn't a bad, because they want to move closer to the spec), but for me as a library developer it is hell to work with the unstable API.

What to do about it; Mozilla started to have their own JS based client that they keep up to date (https://github.com/mozilla-b2g/marionette-js-client), so one of the future tasks will be: removing all the proprietary stuff I build & replace it with this client (which then should help to get rid of nearly all existing issues). Timeline? I don't know. Any help is appreciated.

[hemmerling]

Same here too, English Firefox31 on English Win8.1., 32bit

1. Error ”» ERROR: dalek-browser-firefox: Error starting WebDriverServer, port 9006 in use” if I try one of the two tutorial examples
2. The tip to push the timout from 400 to 4000 or even 8000 does not help, the browser is loaded for a moment, but then the test application breaks with the error is "net.js:1236: throw new Error('Not running');"
3. Btw, the path to Firefox on WIndows seems to be fixed in the node.js module "dalek-driver-firefox", i.e.it look as as if the node.js module does not check the registry, but complains ”» ERROR: dalek-driver-firefox: Binary not found: C:\Program Files\Mozilla Firefox\firefox.exe”, if Firefox is not installed at the default location.
4. With Chrome everything works fine with the two tutorial examples, on Windows. Btw, since a few weeks, on Windows, Chrome refuses to install on Pentium-III system... but just on Pentium-IV and better ( though WIndows 7 runs smoothly on a Pentium-III class Athlon XP2800 CPU compter with 3 GB RAM ).

Sincerely
Rolf

[SumsMystic]

I faced same issue on my Win7x64 Dalek v0.0.5.
Issue temporarily avoided by modifying the timeout as seen in the above comments.

But looks like things are not moving much in DalekJS project after 2014. Is that really the case?