THE SHORT ANSWER
Roblox has released DataModel.ServerLowMemoryWarning, a server-side signal that fires when a live server moves from normal into high memory usage. It repeats every 60 seconds while memory stays elevated, runs on the DataModel task scheduler thread, and is available in live servers and Team Test sessions — but not in Studio playtests or on clients. Developers must write their own cleanup logic; the signal only provides notification.
- Signal fires when server exits normal memory levels into high usage
- Repeats every 60 seconds via internal debounce while memory remains high
- Runs on DataModel task scheduler thread — safe to modify instances
- Only works on live servers and Team Test; no-op in Studio playtests and on clients
- Does not free memory automatically — developers must implement cleanup logic
What Changed
Roblox has shipped DataModel.ServerLowMemoryWarning, a new signal that fires on RCC servers when the memory controller detects the server has left normal memory levels and entered high usage. The signal gives server scripts a chance to free memory before an out-of-memory crash disconnects every player in the instance. It is available starting November 2, 2026.
How the Signal Works
- Trigger point: The internal memory controller flags the server as having moved from normal to high memory usage.
- Cadence: While memory stays high, the signal re-fires every 60 seconds (an internal debounce timer).
- Thread: The event fires on the DataModel task scheduler thread, so handlers can safely access and modify instances.
- Scope: Live servers and Team Test sessions only. It does not fire on clients, during Studio playtests, or in LocalScripts (connecting from a LocalScript is allowed but the signal will never fire).
What Developers Can Do With It
Inside the connected handler, scripts can:
- Destroy temporary debris, particle effects, or other short-lived objects.
- Unload map regions or chunks that no players are near.
- Pause NPC, enemy, or item spawning until memory pressure eases.
- Log warnings to external analytics to identify what drives memory growth over time.
The signal itself does not free memory. If the handler removes nothing, memory usage will not change. Roblox emphasizes this is a notification, not a replacement for memory budgeting — developers should still monitor the Developer Console and fix leaks or unbounded growth in content and scripts.
Limitations and Testing
- No Studio playtest support: Because Studio playtests don't run full RCC server instances, there is no local trigger for testing. Developers must start a Team Test session to verify their handler.
- 60-second window: Cleanup logic should complete well before the next fire; if it exceeds the debounce interval, the server may crash before the handler finishes.
- Client memory not covered: The signal is strictly server-side. Roblox says it will explore additional signals for client memory feedback in the future.
What's Next
Roblox plans to investigate adding similar signals for client-side memory pressure, aiming for full coverage of memory limits on both server and client. The team is collecting feedback and questions on the Developer Forum announcement.