We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
定位到问题所在就是#634的修改导致的,改回浅拷贝就正常运行了 深拷贝会触发结构体内部容器的copy,如果此前dest对应容器内部存储的(如示例FString)数据地址与src对应容器内部存储的(如示例FString)数据地址相同,那么在容器copy时会优先Empty清掉dest内的数据,由于容器内存储数据地址相同,src的也被清了,地址非法,这时再从src向dest拷贝就会崩溃
The text was updated successfully, but these errors were encountered:
非常好issue,使我的code旋转。 #634 是去年7月的更新,我怀疑跟某些后续的更新有逻辑冲突,比如去年11月提交的 e4c36a2
Sorry, something went wrong.
No branches or pull requests
定位到问题所在就是#634的修改导致的,改回浅拷贝就正常运行了
![image](https://private-user-images.githubusercontent.com/31158706/301768790-e42d4a75-babd-445d-a73b-e00e455386d1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEyMjI1MjAsIm5iZiI6MTcyMTIyMjIyMCwicGF0aCI6Ii8zMTE1ODcwNi8zMDE3Njg3OTAtZTQyZDRhNzUtYmFiZC00NDVkLWE3M2ItZTAwZTQ1NTM4NmQxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE3VDEzMTcwMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU5NDhhZDUwMDc3MmNjMzlhOTA1YjQzNGViNGI4ZjRhZjJmZGNiMmFhNGFkZDM2NDEzMDY3NzY4N2NkYTc0ZmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.4X0mTqZaom1U998FJh5vElT1MNms4jm28c1qji75qIE)
深拷贝会触发结构体内部容器的copy,如果此前dest对应容器内部存储的(如示例FString)数据地址与src对应容器内部存储的(如示例FString)数据地址相同,那么在容器copy时会优先Empty清掉dest内的数据,由于容器内存储数据地址相同,src的也被清了,地址非法,这时再从src向dest拷贝就会崩溃
The text was updated successfully, but these errors were encountered: