Springlobby crash when loads game

[silver]

I have a friend that has installed spring 84.0 but when the springlobby load a game, it crash, and appears this error:

"This application has requested the runtime to terminate it in an unusual way."

Spring only works whe he uses spring.exe, to load a game, he can play a complete game without crashes.

His pc specs:
Windows vista home premium X32 SevicePack2
processor intel core duo E4600
Ram 3 gb

the springlobbypreferences, it´s set path to spring.exe, he doesn´t use multhread version (MT).

here is the infologtxt:

[abma]

can you try to change
Edit->Preferences->Spring->Use alternative launch method?

i also made a mantis report: http://springrts.com/mantis/view.php?id=2774

[abma]

is already spring running? or an other program, that uses port 8452?


from infolog.txt:
"[f=0000000] Error: Failed to bind UDP socket on IP , port 8452: Intento de acceso a un socket no permitido por sus permisos de acceso"

and can you please translate the error message?

i guess its something like this: "cannot use socket, its already in use" ?

[hoijui]

"tried to access an invalid socket (invalid due to its access rights configuration)"
nothing about port, but... the message is so general, that it could still be that, i guess. could also be a firewall issue, though, or .. something else.

[silver]

can you try to change
Edit->Preferences->Spring->Use alternative launch method?

He launchs a game when "Use alternative launch option" is actived, but he disabled this option and the crash still happens.

is already spring running? or an other program, that uses port 8452?

spring still running, and no, other program doesn´t use port 8452

from infolog.txt:"[f=0000000] Error: Failed to bind UDP socket on IP , port 8452: Intento de acceso a un socket no permitido por sus permisos de acceso"and can you please translate the error message?

translation:"[f=0000000] Error: Failed to bind UDP socket on IP , port 8452: Attempt to access to one socket, it´s no permited because your permission access"

But the next infolog.txt line says:
[f=0000000] [UDPListener] successfully bound socket on port 8452

The problem starts here:
[f=0000000] recording demo: demos/20111124_225039_deserteagle_84.0.sdf
[f=0000000] PreGame::GameDataReceived: 139 ms
[f=0000000] User number 0 (team 1, allyteam 0)
[f=0000000] Error: DLL information:
[f=0000000] Error: 0x00400000 spring
[f=0000000] Error: 0x77800000 ntdll
[f=0000000] Error: 0x775d0000 kernel32

[hoijui]

i think it is a bug in spring code.
it looks like it assumes binding the socket worked fine, even if it did not, because of an uninitialized bool var (it should be initialized to false, but it being uninitialized gives it a 255:1 chance of being true). in other words, network socket binding failed, but it goes on as if it did not, and then fails later, when trying to read from or write to the socket. the fix is easy, i will do it now, and it will be in the next version.
you should try to figure out why it fails to bind the socket.

[hoijui]

should be fixed by:
https://github.com/spring/spring/commit ... 5ced458cad

this will not make your problem go away, but will make spring work as it should, in the case of such a problem, which is: exit(1)

[silver]

you should try to figure out why it fails to bind the socket.

we tried to open the port for sprinlobby in his modem, but the problem continues.

should be fixed by:https://github.com/spring/spring/commit ... 5ced458cadthis will not make your problem go away, but will make spring work as it should, in the case of such a problem, which is: exit(1)

Can you make a patch please? i want to see if this fix´s the problem.

[hoijui]

as i said, this does not fix your problem. your problem is a local setup problem. this only fixes springs behavior after such a problem already occurred.
the modem not forwarding the port to the PC would not cause such a problem (though it is required for hosting to work of course). a firewall running on the PC itsself could cause that problem, or in theory, insufficient access rights (very unlikely, i think), or something already running on the port, or the address given as host address not being available on the PC.

[silver]

a firewall running on the PC itsself could cause that problem, or in theory, insufficient access rights (very unlikely, i think),

SOLVED!!! we did this:
Like you said it wasn´t sufficient access rights, the firewall wasn´t letting conetions from external red to Pc for spring.exe, springlobby and multithraded, we enable it. But also we configured the firewall to let always connections with the port 8452 this fixed the crash.

THANKS for the help.