Crash on Android with Unreal Engine 5.2

[maamoonm]

Describe the bug

When Using Transfer Manager Download with Unreal Engine 5.2 on android platform, getting 'Pointer tag for 0x7009d7c5d0 was truncated.'

Using AWS SDK CPP 1.9.379.

tried using CUSTOM_MEMORY_MANAGER, did not work also.

On UE4.26 no issues on Shipping and Development for both windows and android.
On UE5.2 Development build no issues at all, but always crashes on shipping,
On Windows UE5.2 no issues for both Shipping and Development.

Expected Behavior

not Crashing

Current Behavior

Starts downloading, and at some random point when downloading it crashes with below dump
Abort message: 'Pointer tag for 0x700e238ec0 was truncated.'
#00 0x000000000004e574 /apex/com.android.runtime/lib64/bionic/libc.so (abort+180) (BuildId: 47654091281bdd4362effe3ca962c8df)
#1 0x000000000003bb68 /apex/com.android.runtime/lib64/bionic/libc.so (free+96) (BuildId: 47654091281bdd4362effe3ca962c8df)
#2 0x00000000000b0f40 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_key_clean_all()+136) (BuildId: 47654091281bdd4362effe3ca962c8df)
#3 0x00000000000b0968 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_exit+72) (BuildId: 47654091281bdd4362effe3ca962c8df)
#4 0x00000000000b083c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+68) (BuildId: 47654091281bdd4362effe3ca962c8df)
#5 0x00000000000505d0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 47654091281bdd4362effe3ca962c8df)

Reproduction Steps

Start Application, Download file from s3 using Transfer Manager

Possible Solution

No response

Additional Information/Context

No response

AWS CPP SDK version used

1.9.379

Compiler and Version used

VS 2022

Operating System and version

Android

[maamoonm]

Found out that adding FORCE_ANSI_ALLOCATOR=1 solves the issue

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.