Hello,

My server will not save. It used to work, but I haven't used this server until recently, so I can't tell you with which ALiVE version or Arma version it stopped working with. I hit save and exit, the tablet comes up, but it doesn't go any farther than here:

http://i.imgur.com/X7NL3b4.jpg

Here is the alive plugin from a recent test running only @CBA, @ALiVE, and @AliveServer:

http://pastebin.com/qq2bjLCb

And my RPT:

http://pastebin.com/3v2asdKS

I have also tried re-installing @ALiVE, @AliveServer and the alive.cfg to no avail.

I've tried both with and without HC and have tried restarting the server multiple times.

Title says it all. Server was performing fine, then after saving and loading the server both the players and AI are rubber-banding all over the place with low ping/ high fps. Don't know if this has anything to do with the persisted mission, but I thought I'd try here.

IIRC a memory leak was introduced to Arma in update 1.54 and still hasn't been fixed.

http://alivemod.com/forum/1826-so-you-want-a-map-indexed-start-here

I seem to be having an issue which may be related to this.

I've been working on a community mission for a few days now using custom created factions. When using the Asymm Commander in conjunction with Civs, the road blocks spawn vanilla guerrilla opfor units.

When I remove the civ modules, roadblock spawn the correct units.

When I put the civ modules back but then change the commander to Invasion or Occupation, the roadblocks work correctly.

But running an Asymmetric Commander and the civ modules at the same time consistently spawned the incorrect units that the roadblocks.

I tried to re-create this using only @Alive and @CBA, but everything seemed to be spawning correctly. I've come to the theory that it must be something to do with non-vanilla factions in conjunction with the Asymmetric Commander. I believe I have followed the faction mapping correctly, would you guys mind taking a look to see if it has anything to do with the config?

http://pastebin.com/4HUD0KA1

So does the player and that same player flying around in Zues count as 2 players? Its frozen on me when doing that.

Are you guys sure you're using CBA 2.3.0 and not 2.3.1? I had zero freezes with 2.3.0 when before the server froze in 10 minutes. After updating to 2.3.1 the server froze after 20 min. I will try reverting back to 2.3.0 and see what happens.

Hi guys.

I have tested with 1.54 running only @ALiVE, @CBA, and @AliveServer and my server froze around 7 hours 30min. With @ace the server froze anywhere from 10min to 1 hour. Therefore it appears to me that @ace is not the issue, it just makes the issue worse.

More info can be found here:

This is a follow-up to my post on the BI forums.

Hi guys, I know others have been reporting this already, but it seems that ALiVE is causing dedicated servers to freeze up. With ACE it freezes after 10 min to 1 hour. I have recently tested only running @ACE, @CBA, and @AliveServer and the server froze at 7 hours 30 min. I should note that the freeze happens when units begin to spawn in, it will not freeze if one is just running the server and nothing is happening. So it seems as tho ACE is not the problem, it just makes the problem worse.

This is what is spammed in my RPT at the time of the crash:

11:32:51 Server: Network message 839f is pending
11:32:51 Server: Network message 839f is pending
11:32:51 Server: Network message 83a0 is pending
11:32:51 Server: Network message 83a1 is pending
11:32:51 Server: Network message 83ad is pending
11:32:51 Server: Network message 83b6 is pending
11:32:51 Server: Network message 83b6 is pending
11:32:51 Server: Network message 83b6 is pending

Mission File:

Arma 3 RPT:

ALiVE Plugin Log:

My community has not had this problem in the past, it only seemed to just start happening in the recent weeks, possibly after the 1.54 update. Based on some research, this issue may not be due to ALiVE but perhaps a memory leak was introduced in 1.54, and ALiVE is simply making this problem more apparent. Figured I might as well bring it to your guys attention anyways with the hopes there might have a fix. Thanks for all your hard work, ALiVE team!