FAForever Forums
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Login

    Two games stopped playing ~40 minutes, and no connectivity screen. Everyone affected, no one hard locked. Exit Code -1.

    Scheduled Pinned Locked Moved
    Game Issues and Gameplay questions
    2
    11
    731
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DoompantsD
      Doompants
      last edited by

      Oof.

      Maybe this one is going to require a lot more troubleshooting on our end, but here goes with what we have:

      Two back-to back games on Friday night hit a point around ~40 minutes where the game action froze like it was paused. No one was hard-locked up (everyone could still select units, move camera, open menus, etc).

      • Same players we play with every week.
      • No new mods. Same we play with every week. (BlackOps suite, Phantom-X, various UI mods.)
      • None of us could exit cleanly. When we finally closed our copies of FA we all ended up on a black screen and had to task manager out. The error was listed as Exit Code -1.

      We've certainly had crashes before, but I've never seen one like this that doesn't result in a connectivity window popup.

      I'm Including the logs. I will try to see if I can recreate the issue another time with the vanilla game, but everyone was kind of disheartened after two failed 40 minute games tonight. I'll also turn on the advanced logging for next time. Thx y'all.

      game_20375889.log
      game_20375645.log

      1 Reply Last reply Reply Quote 0
      • JipJ
        Jip
        last edited by

        There's this:

        warning: Connection dialogue opening due to disconnection by players:
info: Rabid_Donkey

        But not sure whether that is because he actually left at that point. On top of that there's tons of errors, BlackOps didn't receive an update yet of course. I've had this problem too once, it showed like this:

        2493f47d-97dc-43ef-b909-25e09f14b153-image.png

        A work of art is never finished, merely abandoned

        1 Reply Last reply Reply Quote 0
        • DoompantsD
          Doompants
          last edited by Doompants

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • DoompantsD
            Doompants
            last edited by

            Nice catch. I dug up the ICE log, and I notice the same player (Rabid Donkey) shows up first in both logs.

            Think this is this something that can be fixed with a reinstall? (Or even something easier?)

            Also, thoughts on why we all had to use task manager to exit the game? Is that normal for this kind of error?

            ice-adapter.log

            (problems are seen at 2023-07-14 21:03:12.922 and again at 2023-07-14 22:07:40.052 )

            1 Reply Last reply Reply Quote 0
            • DoompantsD
              Doompants
              last edited by

              And yes --- that's very much what our f11 screen looked like too.. No one showed as being behind, or high ping or anything. looked like a normal game.

              1 Reply Last reply Reply Quote 0
              • DoompantsD
                Doompants
                last edited by

                Ugh.. @Jip I know there's some weird connect stuff going on, but this happened again a third time tonight in another PhantomX game, so I'm starting to think it's Phantom related.

                This time it was a different player (Vaemas) showing up first on the ICE log, even though it was mostly the same crew.

                2023-07-28 20:41:04.893 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:41:18.754 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:42:11.007 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:42:32.773 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:43:04.894 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:43:18.754 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:44:11.007 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:44:32.774 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:45:04.894 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:45:18.758 INFO  Sent turn refresh request. (c.f.i.ice.PeerTurnRefreshModule:72)
2023-07-28 20:45:45.870 WARN  Didn't receive any answer to echo requests for the past 10 seconds from Vaemas, aborting connection (c.f.i.i.PeerConnectivityCheckerModule:102)
2023-07-28 20:45:45.871 WARN  Sleeping refreshThread was interrupted (c.f.i.ice.PeerTurnRefreshModule:80)
2023-07-28 20:45:45.871 WARN  ICE Vaemas(349568): ICE connection has been lost for peer (c.f.iceadapter.ice.PeerIceModule:336)
2023-07-28 20:45:45.871 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.871 INFO  Sending Notification:{"method":"onConnected","params":[13857,349568,false],"jsonrpc":"2.0"} (com.nbarraille.jjsonrpc.JJsonPeer:529)
2023-07-28 20:45:45.871 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.871 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.871 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.871 INFO  Sending Notification:{"method":"onIceConnectionStateChanged","params":[13857,349568,"disconnected"],"jsonrpc":"2.0"} (com.nbarraille.jjsonrpc.JJsonPeer:529)
2023-07-28 20:45:45.871 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.871 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.871 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.872 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.872 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.872 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)
2023-07-28 20:45:45.872 WARN  ICE Vaemas(349568): Received invalid packet, first byte: 0x0, length: 65536 (c.f.iceadapter.ice.PeerIceModule:432)

                That's a snip from the log where it died (again, near the 40 minute mark, but this is also shortly after the Phantom X reveal timer we have)

                I'll attach the full logs too, but any suggestions you have, I'm listening. Next week, we'll try a Phantom X game without BlackOps, but right now it seems we can play other games with BlackOps, it's only our phantom X games that are crashing like this. We're big BlackOps fans, so obviously we hate to have to turn it off, but let me know if there's anything we can try to test for you.

                ice-adapter.log
                game_20472476.log

                1 Reply Last reply Reply Quote 0
                • DoompantsD
                  Doompants
                  last edited by

                  So an update on what we've found:

                  This is definitely BlackOps related, but it started recently, and I don't believe BlackOps has been updated in a while so maybe it's something in the main game has changed that broke BlackOps?

                  Phantom-X is not the only mod that locks us in this loop. We recently played a survival map (Survival 5thdimension 16 player v5) and experienced the same freeze.

                  Both cases, the freeze only happens with BlackOps on. If we play Phantom-X or the Survival map in Vanilla, no freeze.

                  Both cases, the freeze happens when people are well into T3/experimental production, though we haven't been able to identify any one unit or action that may have been the reason for the freeze.

                  1 Reply Last reply Reply Quote 0
                  • DoompantsD
                    Doompants
                    last edited by

                    Note a post currently below this one saying they had the same crash/freeze in a campaign map with BlackOps on.

                    1 Reply Last reply Reply Quote 0
                    • DoompantsD
                      Doompants
                      last edited by

                      Here is the log from the Survival Map + BlackOps that crashed. The crash happened about ~30+ minutes into the game, at around 21:30 timestamp I think. That's when there's a bunch of info in the ICE log.

                      71dcd911-09ce-4fe8-9885-4aa8ee0f0801-game_20611540.log
                      0b06e82a-a16a-4e20-a9a9-8d1bb2308fe6-advanced-ice-adapter.log

                      (these are the logs you want, right @Jip? I am assuming advanced ICE log is part of having the debug mode turned on)

                      1 Reply Last reply Reply Quote 0
                      • JipJ
                        Jip
                        last edited by

                        @Doompants the release is out:

                        • https://forum.faforever.com/topic/353/blackopsfaf-unleashed-only-for-faf-v24/121

                        Try again, it is likely related to the bugs that are now fixed

                        A work of art is never finished, merely abandoned

                        DoompantsD 1 Reply Last reply Reply Quote 1
                        • DoompantsD
                          Doompants @Jip
                          last edited by

                          @jip Will definitely test it out. Thanks as always to you and @Uveso for getting on this stuff!

                          1 Reply Last reply Reply Quote 1
                          • First post
                            Last post