TAutoPtr uses default copy / move constructors which can cause dangling references.

This means there are a number of cases (copying auto pointers in inner scopes, passing auto pointers by value, etc) where the underlying pointer can be freed when one instance is destroyed, but the other instances are still pointing to that garbage data.

Steps to Reproduce

TAutoPtr has been deprecated.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-34117 in the post.

Login to Vote

ComponentUE - Foundation - Core
Affects Versions4.124.13
Target Fix4.15
Fix Commit3195119
Main Commit3228932
CreatedAug 2, 2016
ResolvedDec 6, 2016
UpdatedApr 27, 2018