Memory leak and hook flooding

2026-01-20T19:20:42Z

Hello,

I saw this behaviour on my production server, but proved it with a fresh installation of rust-server and carbon framework. The map (3000) is new procedural generated. No players are on the server (except me as admin) and no items deployed at all.

But: As the carbon-console-command "plugins" shows, DeployableNature consumes 1000x more hook events than other plugins, and the memory is constantly growing. On my production server it was 3GB after 2 or 3 days, and it will lead to a out of memory crash, if you are not restarting the rust-server at a regular basis.

Greetings,
Toli

plugins.txt

2026-01-20T21:38:55Z

Wow, see attached plugins.txt, after 3 hours of runtime, DeployableNature consumes 8 GB of "hook memory". Without a single Item deployed.

plugins.txt

2026-01-20T22:15:22Z

You don't happen to have any data as to what hooks are causing the issue by chance?

The hooks I subscribe to (for the most part) should only be running when players are on the server.

OnActiveItemChanged - Can be disabled by setting the following config option to false: "Display a chat message when a player pulls out a hammer for the first time, reminding them that they can remove deployables"

CanNpcEat
OnItemRecycle
OnDispenserGather
OnDispenserBonus
OnCollectiblePickup
OnLootSpawn
OnPlayerDeath
OnPlayerAttack
OnMaxStackable
CanCombineDroppedItem
OnServerInitialized - Triggered when the plugin starts.
OnMeleeAttack

OnNpcTarget - Heavy - Can be disabled by setting "Prevent wild animals from targeting and killing deployed animals?" to false.

OnEntityKill
OnEntityTakeDamage
OnEntityDeath
OnEntityBuilt
CanBuild

OnPlayerInput - Very heavy - Can be disabled by setting "Allow players to use their middle mouse button to remove an item with a hammer (they can still use chat command regardless if they have perms)" to false.

OnServerSave

2026-01-21T08:54:48Z

10 hours ago, imthenewguy said:

You don't happen to have any data as to what hooks are causing the issue by chance?

Well, looking deeper I think I found the problem. It's the plugin RoamingNPCs which constantly calls the hook "IsDeployableNature". I have only 8 NPCs configured to run around on the map and collecting resources, which seems to create this huge overload.

Is this a problem of DeployableNature or RoamingNPCs? Who will solve it?

2026-01-21T09:59:37Z

What method are they using to call the IsDeployableNature method?

Are they doing a HookMethod call from their plugin (DeployableNature.Call("IsDeployableNature", entity)?

or are they doing Interface.Oxide.CallHook("IsDeployableNature", entity)?

I can add some optimizations to filter out simpler queries such as entities that have no skin ids, but ultimately it would be up to the NPC plugin to reduce it's checks (IE caching entities that it has already checked etc).

Edited 1 hour ago by imthenewguy

2026-01-21T10:46:27Z

Well, as far I can see they define a method and use it in their code. I will only give this small general code example, because it's not open source. I asked them to have a look here in this support ticket an maybe contact you.

...
public bool IsDeployableNatureEntity(BaseEntity entity) => DeployableNature?.Call<bool>("IsDeployableNature", entity) ?? false;
...
...
private bool CheckResources(BaseEntity resource)
{
    if(resource == null) return false;
    if (instance.IsDeployableNatureEntity(resource)) return false;
    ...
}

Sign In

Memory leak and hook flooding

ToliburtiX 2

ToliburtiX 2

imthenewguy 1,073

ToliburtiX 2

imthenewguy 1,073

ToliburtiX 2

Downloads

Customers

Files Sold

Payments Processed

Customers

Providers

Resources

About Us

Important Information