# about a potential issue involving excessive UDP Messaging logs and Out-of-Memory crashes.

**URL:** <https://forums.unrealengine.com/t/about-a-potential-issue-involving-excessive-udp-messaging-logs-and-out-of-memory-crashes/2853103>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, question\
**Created:** [November 10, 2026, 3:59am UTC](https://forums.unrealengine.com/t/about-a-potential-issue-involving-excessive-udp-messaging-logs-and-out-of-memory-crashes/2853103 "2026-11-10T03:59:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![zyouhou1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@zyouhou1](https://forums.unrealengine.com/u/zyouhou1)\
**Post date:** [November 10, 2026, 3:59am UTC](https://forums.unrealengine.com/t/about-a-potential-issue-involving-excessive-udp-messaging-logs-and-out-of-memory-crashes/2853103/1 "2026-11-10T03:59:08Z")

</div>

Hello Epic Games Support Team,

We would like to inquire about a potential issue involving excessive UDP Messaging logs and Out-of-Memory crashes.

We found the following forum discussion:

> [@FUdpMessageProcessor log spam causing Physical OOM PC crash - what services send these logs?](https://forums.unrealengine.com/t/fudpmessageprocessor-log-spam-causing-physical-oom-pc-crash-what-services-send-these-logs/2711460):
>
> We experienced Out of Memory crashes on several of our users’ machines a couple days ago within our network, all around the same time. This only happened to users on 5.7.2 (we also support the use of 5.4, but this wasn’t present in users using that engine). What we noticed in each of their crash logs was variations of this UDP message spammed millions of times, causing the crash logs to be several GB in size in each case. The IPs in each case were varied, but the spam were variations of this mes…

In this discussion, an Epic developer mentioned that a similar issue had already been fixed in the ue5-main branch as of March 4, 2026.

Could you please clarify the following points?

Has the fix mentioned in the discussion been integrated into Unreal Engine 5.8?  
If so, could you provide the corresponding changelist number or issue reference?  
If the issue has not yet been resolved in Unreal Engine 5.8, is a fix planned for the next release (e.g., Unreal Engine 5.9)?  
If so, could you provide an estimated release timeline or any relevant issue reference?  
In the meantime, is there any recommended workaround or configuration change to prevent this issue in Unreal Engine 5.8?

We would appreciate any official information regarding this issue and its planned resolution.

Thank you for your support.