[Bug] SetPlayerRoutingBucket instantly leaking all system memory

[hasitotabla]

Summary

When using SetPlayerRoutingBucket (I didn't test the entity setter, but it probably will do the same.) with numbers near the signed integer limit, the server starts to leak/reserve all the system memory.

Issue type

Server

Repro rate

Always

Server build version

b111-ea

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

Win 11

CPU

Ryzen 7 3700x

RAM

32GB DDR4

Using txAdmin?

Yes

Hosting provider

Self-hosted

Machine type

Dedicated

/perf endpoint output

DDoS protection

No

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

-- just runcode this on the server
SetPlayerRoutingBucket(1, 2147483647)

-- I use this personally, so I could give each player their own isolated dimension with offset to specific "sub-dimensions".

local NUM_OF_PLAYER_ISOLATED_DIMENSIONS = 25
local function getPlayerIsolatedDimension(playerId, offset)
    assertf(type(playerId) == "number", "Arg #1 (playerId) @ getPlayerIsolatedDimension expected number, got %s", playerId)
    assertf(type(offset) == "number", "Arg #2 (offset) @ getPlayerIsolatedDimension expected number, got %s", offset)

    return 2147483647 - ((player - 1) * NUM_OF_PLAYER_ISOLATED_DIMENSIONS) - (offset - 1)
end

Expected Behavior

Not to reserve all the memory of the system lol.

Actual Behavior

Reserves/Leaks all the memory of the system.

Evidence

Additional Context

No response

[Rodhin]

I've tested and can confirm this happens in Lua but not in JS.

[wolfram-cfx]

Thanks, we are looking into this.

[Gogsi]

A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help!