TS client crashes while connecting to the server

[RedFoxxo]

System Information

Operating System: ArchLinux Operating System Type (x86|x64): x86_64 TeaSpeak Version: 1.1.25 beta 7 (ts3dump_1526627964322) and before

Issue

Reason for reporting this issue: Bug

Detailed Description: TeamSpeak3 client crashes about 1 time out of 8 when connecting to a TeaSpeak server

Client dumps here: crashdumps.zip _(latest is ts3dump1526627964322) Server logs here: log_2018-05-18_09_07_40_general.log (only the latest)

[WolverinDEV]

Should be fixed.

BTW: I cant do anythink with the crashdump of the client :/ I dont have any TeamSpeak sources :)

[RedFoxxo]

Unfortunately the client continues to crash on 1.1.26 beta 5

This is what happens on the server:

[19:44:15] [DEBUG]   1 | [151.18.97.185:29080/RedFox]Client ping timeout (15439)
[19:44:15] [DEBUG]   1 | [151.18.97.185:29080/RedFox]Attemp to close connection. (Flush data: 1)
[19:44:15] [DEBUG]   1 | [151.18.97.185:29080/RedFox]Awaiting write prepare, write and acknowledge queue flushed
[19:44:15] [DEBUG]   1 | [151.18.97.185:29080/RedFox]Write prepare queue progressed
[19:44:15] [DEBUG]   1 | [151.18.97.185:29080/RedFox]Write and acknowledge queue flushed
[19:44:15] [INFO]   1 | Client RedFox (151.18.97.185:29080) disconnects. (UID: dJKdU8NNyGdnjWzEPCzE+Qv1VEI= Database ID: 3)

Full server log here: log_2018-05-20_15_49_22_general.log

[WolverinDEV]

Do you have the crash message of the client? (Start the client with the -console parameter)

[RedFoxxo]

At the moment I couldn't recreate the error but I managed to crash the entire server xD Logs: log_2018-05-20_15_49_22_general.log Dump: crash_dump_1f3884b9-e3eb-4a9a-d914f98a-f72b8074.zip It happened when I stopped the id 1 server from yatqa I know it has nothing to do with the title of this thread but I'm lazy. LOL.

EDIT1: I managed to crash the client but the console closed immediately before the crash report

EDIT2: But looking at the logs I found this. I hope it is useful. (Yeah the time is wrong, idk why)

2018-05-20 20:03:18.537895|INFO    |ClientUI      |1  |Lookup finished: ip=79.143.183.2 port=9987 query=support.thebunny.eu error=0
2018-05-20 20:03:18.537895|INFO    |ClientUI      |1  |Resolve successful: 79.143.183.2:9987
2018-05-20 20:03:18.537895|INFO    |ClientUI      |1  |Initiating connection: 79.143.183.2:9987
2018-05-20 20:03:18.563802|INFO    |ClientUI      |1  |Connect status: Connecting
2018-05-20 20:03:20.021118|DEVELOP |PktHandler    |   |Puzzle solve time: 2
2018-05-20 20:03:20.387310|INFO    |ClientUI      |1  |Connect status: Connected
2018-05-20 20:03:20.406249|CRITICAL|SCHandler     |1  |Assertion "m_connectStatus == STATUS_CONNECTED || m_connectStatus == STATUS_CONNECTION_ESTABLISHING" failed at c:\jenkins\workspace\client\clientwindows\deps\teamspeak_client_lib\src\serverconnectionhandler.cpp:3338; 
2018-05-20 20:03:20.464072|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 104.28.31.195:41144
2018-05-20 20:03:20.465070|INFO    |TSDNS         |   |No TSDNS found
2018-05-20 20:03:20.514938|        |KeyBindings   |   |Default monitoring disabled

EDIT3: I want to be sure I have provided all the data. Full client log here: ts3client_2018-05-20__22_02_03.500020.log

EDIT4: I'm still on 1.1.26 beta 5. I'll update tomorrow.

[WolverinDEV]

Ahh yeah thats a really rare error (i just could produce it in 1 out of 100) The problem is that i need to know which packet causes that, and i still now updated my TS3 protocol hook to linux :D

[WolverinDEV]

Should be fixed (found a (the) logic error) Will be released within the next version

[WolverinDEV]

Should be fixed