The reason for this seems to be that the player list is sent to all clients whenever a player respawns - at this point that is wasteful though, because the playerlist hasn't changed. The underlying issue is that ClientNewEventTypeID fires for new players (where sending the playerlist makes sense since it has actually changed) as well as respawning players (here, the playerlist hasn't changed).

Hello VTrayxX.
Please click on "Show and prepare report" when the crash occurs and upload the generated archive to this ticket.

Well..... Server went down for a windows update...
4.2Gb of ram usage is back..
Been about an hour and still sitting at 4.2gb

Dont consider. Hearing whilst uncon is unrealistic.

Must have been doing some background process...
it's now back down under 1gb of usage after 3 hours.

Yeah I get that, You're also quoting a community wiki...

Exactly the same problem!

2 years and 6 months.
This feedback tracker is for game as officials servers. I am not interested in community servers at all.

Please tell us in details what do you mean by HeadingModel?

This was fixed from the unrealistic telepathic bug few patches ago.
100% should NOT hear while uncon.

Those haven't had loot in a long long time.
It's commented out in the proto file.

object name: mil_tower_small

Possible improvements to this will be released with the upcoming experimental that will be releasing soon!

In T176819#2535173, @Geez wrote:

Hello.
We plan to deploy a fix for this as part of an additional patch for our 1.23 update, which should be deployed very soon. We highly encourage you to try it out on the Experimental branch.

Hi Geez,

I have the same problem. A random player appears at the end, exactly the same. It happens once a day on average. It happens randomly. I don't know what the problem is. Almost all my crashes are like this

Hello auxOlives.
The crash is related to the modded content you are running. Specifically there is a problem with some weapon that is attached to some clothing.

Hello NIGHTMARE_DAYZ.
This appears to be caused by some mod you are running. Unfortunately we cannot tell which mod is it besides that it crashes on HeadingModel.
The mod creator will have to fix the problem on their end.

Thank you, we will investigate with BattlEye.

Thank you, we will investigate with BattlEye.

We also plan to release the fix above in the upcoming experimental which should be deployed very soon. We highly encourage you to try it out on the Experimental branch.

Hello.
We plan to deploy a fix for this as part of an additional patch for our 1.23 update, which should be deployed very soon. We highly encourage you to try it out on the Experimental branch.

Hello.
We plan to deploy a fix for this as part of an additional patch for our 1.23 update, which should be deployed very soon. We highly encourage you to try it out on the Experimental branch.

Hello.
We plan to deploy a fix for this as part of an additional patch for our 1.23 update, which should be deployed very soon. We highly encourage you to try it out on the Experimental branch.

Hello.
We plan to deploy a fix for this as part of an additional patch for our 1.23 update, which should be deployed very soon. We highly encourage you to try it out on the Experimental branch.

You literally cant break bones with melee. If a player already has a broken leg and you punch it it will make the sound but you cannot cause a break.

"-Able to break bones with melees" I've already broken a leg with the melee
"-Melee headshots should do more damage and have high KO rate(currently there is no head hitbox on players for melee" I think there's a hitbox on the player's head when you do a mele attack.

Reinstalled drivers worked for bit now again doesnt work tired of fixing this problem might even uninstall game and not play for some time you can close the ticket.

I only got one monitor if i understood that right i will try to do clean install of video drivers have not tried that yet.

Hello ClumsyJ13.
The crash dump points towards this - format = 0x00007ff784524d90 "Out of memory.\nYour swap file is too small, only %llu MB of free space left.\nIncrease your swap file size or delete some files from your hard disk\n"

Do you have some non standard setup when it comes to resolution or multiple screen setup? And can you try to do clean install of video drivers?

If i force it to fullscreen it just goes black screen tried that bunch of times, also forgot to mention that tried with buldozer thing too didnt work.

DayZ is fueled by intraction, this would boost interactions and create cool interesting scenarios that no other game could replicate. watching back old clips when this was in the game really showed that it worked well and with no complaints, please consider.

Resolved for the upcoming patch for 1.23 update.

In T175110#2533080, @Steniboy wrote:

@Geez

Steps to reproduce the crash:

• spawn yourself a weapon with an overlayed scope (for example winchester with hunting scope)
• take the weapon in your hands and go prone
• kill yourself while prone (via admin command or let someone shoot you; you need to be in the prone state on death)
• respawn at least once (doesnt matter if you respawn multiple times, its just important you do it at least once)
• leave the server while your original body still hasn't despawned or wasnt cut up
  
  ---> leads to server crash divide by 0 <---
  
  Whats the issue? Since 1.22 your weapon no longer properly detaches from your hands when you die in the prone state. It stays "stuck" in your hands. You cannot loot that weapon and cutting up the body makes the weapon go poof. Weapons with overlayed scopes stuck in your hands are the issue if you respawn at least once and then leave the server before your original body despawns or is cut up. The best solution in my opinion to fix this is to make the weapons detach correctly whenever a player dies while being prone. It will also make that weapon lootable for other players, which should obviously be fixed along.
  
  @Server Owners @everyone As a temporary fix until the Devs address the issue use the following simple Mod (server side only):
  Server_DivisionByZero.pbo1 KBDownload
  
  
  What does this mod do? `modded class PlayerBase { override void EEKilled(Object killer) { super.EEKilled(killer);
  
  GetGame().GetCallQueue(CALL_CATEGORY_GAMEPLAY).CallLater(this.DropItemInHands, 2000); }
  
  void DropItemInHands() { ItemBase itemInHands = ItemBase.Cast( GetHumanInventory().GetEntityInHands() ); if (itemInHands) { int boneIndex = GetBoneIndexByName("RightHand_Dummy");
  
  vector m4[4]; GetBoneTransformWS(boneIndex, m4);
  
  GetInventory().DropEntityWithTransform(InventoryMode.SERVER, this, itemInHands, m4); } } }` It basically detaches any weapon from players hands couple seconds after death and "teleports" it to the ground. This prevents the server from crashing as the weapons with overlayed scopes are no longer attached on dead players. Furthermore it makes the weapons lootable. This was tested for couple days in a row on all KarmaKrew Servers and the crash never occured. Confirmed fixed. Credits to @Maroonchy for the Code.
  
  Sincerely, Sten

Thank you, we will investigate with BattlEye.

Thank you, we are aware of issues with the LA servers and we are working closely with Nitrado to make sure everything is in order.

In T177192#2532455, @JerseyD911 wrote:

@lemmac ;))))))))))))))))))) You are a genius :) So much moves because of a single tundra. Even PPL who lost their 6months bases because of cheaters didn't react that way. Yeah, but you keep on trying my friend, maybe one day you'll have your sniper back

@JerseyD911 Please keep the comments on the topic of the issue - this space is not for trolling and venting frustration.

Thank you, we will investigate with BattlEye.

Hello BabaYega.
Is there any sort of crash? since you have posted the report log. But crashes usually are not connected to in game kicks.

Hello pete420.
Please click on "Show and prepare report" when the crash occurs and upload the files here.
If this occurs only on a specific server then it might be related to the mods the server is running.

Thank you, we will investigate with BattlEye.

Resolved for the upcoming patch for the 1.23 update.