Can't run TS5 on my GTX 1080 Ti

TeamSpeak Client
1

Hello, after i update TS client to 26 beta i can’t run TS anymore…
Today I tried updating to 27 beta and 29 too, and still can’t run TS Client.

After runing TS client i see only blue window, without any text or gui items.

In logs I see that TS process can’t run some GPU processes, can anyone help me?

[1021/155648.699:INFO:crash_reporting.cc(218)] Crash reporting enabled for process: browser
[1021/155648.790:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 1 time(s)
[1021/155648.791:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 2 time(s)
[1021/155648.792:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 3 time(s)
[1021/155648.793:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 4 time(s)
[1021/155648.794:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 5 time(s)
[1021/155648.795:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 6 time(s)
[1021/155648.795:ERROR:browser_gpu_channel_host_factory.cc(153)] Failed to launch GPU process.
[1021/155650.058:INFO:crash_reporting.cc(218)] Crash reporting enabled for process: utility
[1021/155650.111:ERROR:browser_gpu_channel_host_factory.cc(153)] Failed to launch GPU process.
[1021/155708.882:INFO:crash_reporting.cc(218)] Crash reporting enabled for process: browser
[1021/155708.903:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 1 time(s)
[1021/155708.904:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 2 time(s)
[1021/155708.905:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 3 time(s)
[1021/155708.906:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 4 time(s)
[1021/155708.907:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 5 time(s)
[1021/155708.908:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 6 time(s)
[1021/155708.908:ERROR:browser_gpu_channel_host_factory.cc(153)] Failed to launch GPU process.
[1021/155709.251:INFO:crash_reporting.cc(218)] Crash reporting enabled for process: utility
[1021/155709.271:ERROR:browser_gpu_channel_host_factory.cc(153)] Failed to launch GPU process.

Windows 10 2004 with all latest updates installed.
i7-8700k
Samsung 970 Plus NVMe
32Gb Ram
1080Ti (456.71 driver)
My browsers is: Google Chrome (86.0.4240.111) and Microsoft EDGE (86.0.622.48) on chrome engine

2

I would just uninstall it and grab a new one from beta.teamspeak.com. 29.1 just came out not to long ago.

3

Downloaded adn installed it today, befote i open this topic, but downloaded version reported in logs as TeamSpeak Client 5.0.0-beta27 (2020-10-06 14:38:57)

Also tried to reinstall with full wipe (files and registry), it’s not help me with my problem.

Checked again, in new logs it was TeamSpeak Client 5.0.0-beta29.1 (2020-10-21 10:56:24), but problem is still here.

4

The installers on the website are not updated yet and we thing that update will not help.

Did the client work before?
What operation system and graphics card is this happening?

2 Likes
5

yeah, it worked before 26 beta update if I’m not wrong in version.

As i wrote before, my OS is Windows 10 2004 build with all latest updates installed, and my GPU is Aorus 1080TI with latest NVIDIA driver 456.71.

And for more information, I can install update, but I can’t run client after update.

PS: OS lang is Russian.

I update to not working version after chatserver was offline, and client repeatly spam “error” sound, after it, I disable error sounds, and after some days ago I updated client version.
After that update i can’t run client anymore, and forced to use stable TS3 client.

6

@TS.ChrisR
Is there a way to disable hardware acceleration for the webview?
Might be related to the many driver issues gpus have with blink.
I know a lot of people that have to disable hw-accel in chrome for example on a regular basis.

7

@1F33LR41N and @Obbi

For some reasons this only effects a GTX 1080 Ti. We had the same experience.

You could try to run the client with following start parameter –no-sandbox . This solved the issue for us.
grafik

2 Likes
8

yes, this helped to resolve my problem.
in next builds can you resolve this problem without need to add “–no-sandbox” parameter or I need to add it to all next builds?

Anyway, Thank you!

9

AFAIK this is not in our hands. Chromium enables the Sandbox per default.

Leave the parameter there where it is. That’s the only way.

3 Likes
11

For the next beta you can try it without and it should™ work without it (at least we didn’t have to on our test systems that required it in the past).
If it still doesn’t work you can always add it back and let us know.

2 Likes