Race condition in the display argument provider API

[Gama11]

It seems that if a display arguments provider calls the callback too quickly, there's a race condition and the init fails. With vshaxe-build, I was usually greeted with an error message like this when reloading the window:

Haxe language server started
Haxe server restart requested: display arguments changed
Restarted Haxe server: display arguments changed
Listening on port 6000
Listening on port 6000
events.js:163
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE 127.0.0.1:6000
    at Object.exports._errnoException (util.js:1050:11)
    at exports._exceptionWithHostPort (util.js:1073:20)
    at Server.setupListenHandle [as _listen2] (net.js:1263:14)
    at listenInCluster (net.js:1304:12)
    at doListen (net.js:1428:7)
    at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:10)

After which completion wouldn't work anymore.

I don't think I've never experienced the problem with the Lime extension (it needs to launch a lime display process first and read the results from that, so it would take a bit anyway / probably never becomes an issue).

For now I'll just work around this by adding a haxe.Timer.delay() in vshaxe-build, but we need to investigate this and find the cause.

[ncannasse]

Got this just now. I might have overlook it but I didn't see the message "The Haxe server crashed 5 times"

[ncannasse]

Ok, got it again and this time I had the message, seems related to #250 then

[ncannasse]

Was it closed after the release ? Because I still got it with 2.1.0 ;)

[Gama11]

Yes, the fix is not in 2.1.0.

[ncannasse]

When is 2.1.1 :D ?

[Gama11]

Now it's out, but with 2.2.0. :)