# UE 5.7.2 various unreachable code detected when using bEnableAddressSanitizer 

**URL:** <https://forums.unrealengine.com/t/ue-5-7-2-various-unreachable-code-detected-when-using-benableaddresssanitizer/2707239>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [February 6, 2026, 2:06pm UTC](https://forums.unrealengine.com/t/ue-5-7-2-various-unreachable-code-detected-when-using-benableaddresssanitizer/2707239 "2026-02-06T14:06:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [February 6, 2026, 2:06pm UTC](https://forums.unrealengine.com/t/ue-5-7-2-various-unreachable-code-detected-when-using-benableaddresssanitizer/2707239/1 "2026-02-06T14:06:58Z")

</div>

Setting bEnabledAddressSanitizer to true when building Development Editor Win64 uncovers numerous issues with unreachable code in systems as diverse as:

NiagaraEditor

RigVM

TextureGraph

FoliageEdit

SequencerCore

I recommend someone enables the setting and reviews the output in order to determine if the behaviour of these systems is correct or there are unintended sideeffects.

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [February 6, 2026, 2:07pm UTC](https://forums.unrealengine.com/t/ue-5-7-2-various-unreachable-code-detected-when-using-benableaddresssanitizer/2707239/2 "2026-02-06T14:07:02Z")

</div>

**Steps to Reproduce**  
1) Set bEnabledAddressSanitizer to true

2) Compile Development Editor Win64

Observe: MSVC compiler output indicates multiple error C4702: unreachable code

---

<div class="post-metadata">

**Author:** ![ffabian.bl](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ffabian.bl](https://forums.unrealengine.com/u/ffabian.bl)\
**Post date:** [February 7, 2026, 6:06pm UTC](https://forums.unrealengine.com/t/ue-5-7-2-various-unreachable-code-detected-when-using-benableaddresssanitizer/2707239/3 "2026-02-07T18:06:24Z")

</div>

Hello [mention removed]​,

Thanks for the report. I was able to reproduce this locally by building the engine from source in **UE 5.7.2** following the steps you mentioned.

This appears to be a regression since I tested the same setup in **UE 5.6** and was not able to observe the same output there.

I’ll continue looking into this and follow up once I have more relevant information.

Best,

Francisco

---

<div class="post-metadata">

**Author:** ![ffabian.bl](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ffabian.bl](https://forums.unrealengine.com/u/ffabian.bl)\
**Post date:** [February 12, 2026, 12:59pm UTC](https://forums.unrealengine.com/t/ue-5-7-2-various-unreachable-code-detected-when-using-benableaddresssanitizer/2707239/4 "2026-02-12T12:59:52Z")

</div>

Hi ​[mention removed]​,

I looked into this further and ASan for Windows Editor builds isn’t currently a supported workflow. That said, the unreachable code build failures you reported have already been addressed upstream in UE5-Main via several small changes, so you may be able to unblock compilation by integrating those fixes.

I was able to cherry-pick the following CLs into **UE5/Release-5.7** and confirm they eliminate the C4702 build stops:

- CL 45956790 – Fix unreachable code warnings revealed by Editor ASan builds (SequencerCore / ViewModel.h)
- CL 45924069 – [FoliageEdit] Fix unreachable code error
- CL 45836429 – Move binding for OnFinishedChangingProperties into reachable code
- CL 48449262 – RigVM Variable Mapping: remove unreachable code

With these integrated, the Editor target will compile successfully with ASan enabled on 5.7. However, **launching the Windows Editor built with ASan still crashes** (in my case, during startup in the MovieScene/PreAnimatedState path), which prevents the Editor from loading.

Epic’s recommended usage on Windows is to enable ASan only for the Win64 Game/Client target (not the Editor), via \*.Target.cs. For reference, Patrick Laflamme describes that workflow here: [Can't debug project with ASan](https://forums.unrealengine.com/t/cant%5C-debug%5C-project%5C-with%5C-asan/2668998)

I’d suggest enabling ASan only for your **Game/Client** target but if you want to pursue Editor ASan builds for experimentation, the CLs above should help unblock compilation.

Please let me know if this information helps.

Best,

Francisco

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [February 13, 2026, 10:45am UTC](https://forums.unrealengine.com/t/ue-5-7-2-various-unreachable-code-detected-when-using-benableaddresssanitizer/2707239/5 "2026-02-13T10:45:20Z")

</div>

Thanks Francisco, I’ll give those CLs a look!

---

<div class="post-metadata">

**Author:** ![ffabian.bl](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ffabian.bl](https://forums.unrealengine.com/u/ffabian.bl)\
**Post date:** [February 18, 2026, 12:07am UTC](https://forums.unrealengine.com/t/ue-5-7-2-various-unreachable-code-detected-when-using-benableaddresssanitizer/2707239/6 "2026-02-18T00:07:43Z")

</div>

Hi [mention removed]​,

Glad to hear. Please let me know if you need anything further on this case. Otherwise, I’ll go ahead and close it for now.

Best,

Francisco
