Client: TSDNS Crash

[BlackEagle]

Hello,

i need help.

i have download the new TS3 64bit version 3.0.3.

all complete, TS3 runs.

but when i click on a server to join, TS3 didnt work and windows tells me it would not work.

please get help.

thanks

[tingrin]

i just installed teamspeak and when i ty to connect it get this error ....

using windows xp home.

thanks for the help.

[Paradoxical119]

So I was trying to connect to a server, having issues with resolving a hostname, and on a random try, I got a message saying the client had crashed, and now when I try and do it again, my client just crashes. Suggestions?

[dante696]

We know, that there is a problem "on connect"

We call it TSDNS crash and hope to fix it with client 3.0.4 ;(

[Gnarfoz]

Can you elaborate on the problem?
Is it something server administrators can work around?

My 3.0.3 client worked fine until today, while others on my server had this problem for over a week now, and had to downgrade to 3.0.2.

Apparently, the beta channel already has a 3.0.4 build, the changelog says "- Fixed possible crash when connecting to server", yet 3.0.4 still crashes almost immediately after startup. My two auto-connect servers are being connected to, but the client crashes 1 or 2 seconds after startup.

Any pointers?


Thanks
Gnarfoz

[dante696]

This is not fixed yet! We hope to get more informations from our next beta release (Version:3.0.4 (31.01.2012 13:20:02).
This version should be available this afternoon.

[Gnarfoz]

Looks like you squashed the bug. :-)

Works again for me. No word from my other users yet, though.

---------------Merged----------------

No dice, another one experienced the problem with his 3.0.3 client today for the first time, upgraded to today's 3.0.4 build, crashes. :|
Works for me, though.

[Farquharson]

hello, I'm having a problem with my teamspeak, I have no clue what's going on, but sometimes, when attempting to connect to a sever, it crashes my teamspeak. Please see what you can do about this and hopefully you guys can do something about this. Thank you for your time, and I can't wait to get my teamspeak use back.

[dante696]

When attempting to connect to a sever, it crashes my teamspeak.

There are no informations about your operation system and your client version. Also there is no crashdump or any log?
I hope your client is up to date.

[T.S. Excreta]

This happens on both Windows and Linux clients.

Reproducible: Simply start up a server, connect to it with the client and then shutdown or kill the server. Client begins trying to reconnect, after between 10 and 50 retires, it just crashes hard.

I've tested this with 2 friends. They both setup servers and we all connected to them. Each time, after the server was killed, the client would crash after X attempts at reconnecting.

Be nice if this can be confirmed by a dev or a support person. It doesn't really affect whether or not you can use the client, but things shouldn't abnormally crash like this.

No logs available after the crash, it never writes any. There is also never a crashdump dialog like you get with most crashes.

[Gnarfoz]

The original bug this thread was about seems to still be around.
I still get more than a few people (myself included) every week or other week who need to downgrade to 3.0.2 to be able to connect (server upgraded to 3.0.2 just recently, didn't change anything).

[Khalkotaurus]

installing ts3 on a fresh win7 pc, installs both 32 and 64 bit versions however, when i connect to a server it crashes. New pc, so i'm a little nervous...

Any suggestions?

i have previously used a vista client, which ran flawlessly.

thanks
Alex

thread merged

[dante696]

We release client 3.0.6 on Monday the 23th and it would be nice, that we get some feedback about that problem from our community.
The pre-release can be found in our announcement section.

[Gnarfoz]

This crash is still happening with the 3.0.6 release version.


P.S.: The list of allowed file name extensions (which isn't the same as file types anyway) for attachments on this forum is very short.

[Gnarfoz]

This still happens, with client 3.0.8. (And 3.0.7 before it, too.)

Edit by a moderator
Please do not rename the crashdump file! It makes it hard to find out, what client version you use!