This particular crash is fixed by this PR, it is already available in FAF Develop and on Monday part of the patch!

Thanks I refreshed the cache, but logging out and in manually worked.

My error, seems only slightly different in the lines: java.lang.RuntimeException: Forged Alliance Crashed with exit code 1. See C:\ProgramData\FAForever\logs\game_15430702.log for more information at com.faforever.client.game.GameService.lambda$spawnTerminationListener$43(GameService.java:676) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) at java.base/java.lang.Thread.run(Thread.java:832) Hope it helps

@brutus5000 That doesn't make sense because we have been playing for years on the client, and once the account is linked to Steam it cannot be unlinked. He tried to link his account last night and it said it was already linked as well. But that's fair, please look further into the issue later! Have a good night.

@sheikah fix doesn't work

I too have crash at 23:03 MSK. FAF not connected. And at 23.09.2021 FAF have fix and 2 my compuuters begin lagg. 2 comp in another 2 providers in another 2 home. java.util.concurrent.CompletionException: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://hydra.faforever.com/oauth2/token": Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314) at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1803) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1792) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1016) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1665) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1598) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183) Caused by: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://hydra.faforever.com/oauth2/token": Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:784) at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:710) at org.springframework.web.client.RestTemplate.postForObject(RestTemplate.java:436) at com.faforever.client.api.TokenService.retrieveToken(TokenService.java:105) at com.faforever.client.api.TokenService.loginWithRefreshToken(TokenService.java:99) at com.faforever.client.user.UserService.lambda$loginWithRefreshToken$3(UserService.java:86) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1800) ... 6 more Caused by: org.apache.http.conn.HttpHostConnectException: Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:156) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at org.springframework.http.client.HttpComponentsClientHttpRequest.executeInternal(HttpComponentsClientHttpRequest.java:87) at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48) at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:66) at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:775) ... 12 more Caused by: java.net.ConnectException: Connection timed out: connect at java.base/sun.nio.ch.Net.connect0(Native Method) at java.base/sun.nio.ch.Net.connect(Net.java:574) at java.base/sun.nio.ch.Net.connect(Net.java:563) at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:588) at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:333) at java.base/java.net.Socket.connect(Socket.java:648) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:368) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) ... 25 more

@Breezy1 We need logs, especially from the debugger when it involves a crash. See also this topic. For now, make sure to play on the FAF Develop branch.

https://imgur.com/m008i0y make sure it looks like this you can reset it after the steam link!

If it is a hard-crash then it is not. We need the information from the debugger, you can see an example in this post

Danke dir.

Thanks, I'll check it out

i have that same problem

I've sent a pm.

They offloaded some stuff to other threads mid-development, even if the effect doesn't look too big nowadays I think the game would've been pretty unplayable if they didn't do it. Some info about it: http://www.slideshare.net/guest40fc7cd/threading-successes-02-supreme-commander There were some benchmarks that compared single vs multithreaded performance of supcom during the launch era too, running it multi-threaded had quite big advantages. Saw it some time ago but can't find it now.

Please share the report of the debugger tool - we're already on top of one specific hard-crash that so far the majority of the reports indicated.

That is a crash code that I have not seen before. Does anything in this issue on Github sound familiar? edit: added link

We need the full log of the debugger - please share that with us next time it happens. We're on top of one particular issue that causes a lot of hard-crashes (90% of the reports so far are related to that one particular file), that will be hotfixed next Monday.

ВСЕ УСТРАНИЛ ПРОБЛЕМУ .... ОКАЗАЛОСЬ ПОСЛЕ ОБНОВЛЕНИЯ ВИНДОВС МОИ КЛИЕНТ ВВЯЗАЛСЯ В КОНФЛИКТ С ЗАЩИТОЙ КОМПА ЗА ЧТО И БЫЛ УДАЛЕН И ЗАБАНЕН К НОВОЙ УСТАНОВКИ