Memory Leak causing System Crash

[lassade]

I'm on a027a0e;

I'm debugging a zig program, I only have a couple of windows open, and a single debug info loaded for my exe. Addind the "r" variable in the watch window makes raddbugger to consume +64GB of ram (I have 32) in a couple of seconds my system freezes and I can't do anything except a hard reset.

At frist I though this was an issue when I hit a breakpoint in some specific portion of my code, but I just crashed again without running anything, just by adding the "r" variable in the watch window.

Any ideas? What I can do? I belive I'm running built rad on release, does debug mode have safe guards for this ramped memory leak?

[lassade]

1. Changing the variable name still triggers the issue
2. Debug mode, makes the leak way slower, so I can kill rad before it crashes my system
3. On c1b3461 issue persist

[ryanfleury]

Yikes, not great. What version hash are you running?

…

-Ryan

On Thu, Jun 25, 2026 at 2:48 PM Felipe Jorge ***@***.***> wrote: *lassade* left a comment (EpicGames/raddebugger#850) <#850 (comment)> 1. Changing the variable name still triggers the issue 2. Debug mode, makes the leak way slower, so I can kill rad before it crashes my system — Reply to this email directly, view it on GitHub <#850?email_source=notifications&email_token=AC7ASGME7ZWYHW5ATLS7ZS35BWFYRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBQGQYDCMRZGQZ2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4804012943>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7ASGLNQJQHSOINXTMCLTL5BWFYRAVCNFSNUABFKJSXA33TNF2G64TZHM3TIMJWGI2TGMJQHNEXG43VMU5TINZUG4ZDKNBVGAZKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AC7ASGL4GIL5EHKBR4TLGUL5BWFYRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBQGQYDCMRZGQZ2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AC7ASGMCYXWA7J6LRVOWNE35BWFYRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBQGQYDCMRZGQZ2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[lassade]

I did try with c1b3461 (current master) and with the old commit a027a0e

I did a bit of debugging and it looks like one of the async_thread_3 gets stuck in a infinite loop at fully_qualified_from_rdi_string_and_container

I tried to delete the RDI but the issue persists

[ryanfleury]

That is extremely helpful, thank you! Can you send me the RDI? I will take a look.

…

-Ryan

On Fri, Jun 26, 2026 at 3:57 AM Felipe Jorge ***@***.***> wrote: *lassade* left a comment (EpicGames/raddebugger#850) <#850 (comment)> I did try with c1b3461 <c1b3461> (current master) and with the old commit a027a0e <a027a0e> I did a bit of debugging and it looks like one of the async_thread_3 gets stuck in a infinite loop at fully_qualified_from_rdi_string_and_container image.png (view on web) <https://github.com/user-attachments/assets/58f95887-4f01-42bc-b9ea-2b2e7f577ba3> I tried to delete the RDI but the issue persists — Reply to this email directly, view it on GitHub <#850?email_source=notifications&email_token=AC7ASGNR5IEIIS6XNT6YJQL5BZCIZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBQHA2DQNJRGE22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4808485115>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7ASGOXLGMUTH4YVYXF6435BZCIZAVCNFSNUABFKJSXA33TNF2G64TZHM3TIMJWGI2TGMJQHNEXG43VMU5TINZUG4ZDKNBVGAZKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AC7ASGNYNQD3MZM3HDKLRLT5BZCIZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBQHA2DQNJRGE22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AC7ASGNYLSENJAIGNES7DJT5BZCIZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBQHA2DQNJRGE22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[ryanfleury]

Still not sure why this RDI is malformed like this, but I've added cycle-detection in the "fully qualified string generation" path (it hops across containers and builds a fully namespaced string - in principle these can cycle, although valid RDIs should not have that). So hopefully this should not happen anymore - would you mind trying top of master and letting me know if the same issue persists? Thanks.

[lassade]

I couldn't reproduce the bug with the lastest master 0e2b4ac

I also sent you the rdi via email