SIGSEGV occurs in __memcpy_aarch64_simd after system update on some models (Z Fold6 5G, S24 Ultra)

Question

Hello, I am contacting you because I have a forced termination issue and need to respond. Currently, after the system update on the Samsung Galaxy Z Fold6 5G (samsung q6q) and Samsung Galaxy S24 Ultra (samsung e3q) models, I have a forced termination issue in the Flexcaster app and need to respond. Using the library : Amazon IVS Broadcast SDK: Android 1.23.0 https://play.google.com/store/search?q=%ED%94%8C%EB%A0%89%EC%8A%A4%EC%BA%90%EC%8A%A4%ED%84%B0&c=apps

ID : googletester PW : devAnd@1004

It does not occur in the latest system update of other models, but only in this model. Do you know the cause? The log is as follows.

Build fingerprint: 'samsung/q6qksx/q6q:14/UP1A.231005.007/F956NKSS1AXIA:user/release-keys' Revision: '11' ABI: 'arm64' Processor: '7' Timestamp: 2024-10-30 18:56:55.788362056+0900 Process uptime: 11s Cmdline: kr.co.flextv.streamer pid: 11831, tid: 12725, name: CodecLooper >>> kr.co.flextv.streamer <<< uid: 10682 tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE) pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY) signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x0000006cd7bd4000 x0 0000006cd7bd5000 x1 b400006cd7bd3f80 x2 000000000000eff0 x3 0000006cd7cb5f80 x4 b400006cd7be3000 x5 0000006cd7cc5000 x6 b400007156333be0 x7 0000006cd96542e9 x8 00000000000f0000 x9 0000000000000500 x10 0000000000000300 x11 0000000000000300 x12 0000000000000500 x13 0000000000000000 x14 0000000000000000 x15 00000b46084056ed x16 000000733b5fa4e8 x17 000000732a91e280 x18 0000006cd8b52000 x19 0000006cd96543b4 x20 b4000072364d9280 x21 b4000072364d9260 x22 0000000000000001 x23 0000006cd7bd5000 x24 b400006cd7af3000 x25 0000000000000000 x26 0000000000000014 x27 000000000000002c x28 0000006cd96543a0 x29 0000006cd9654470 lr 000000733b59e354 sp 0000006cd9654320 pc 000000732a91e394 pst 0000000020001000 14 total frames backtrace: #00 pc 0000000000054394 /apex/com.android.runtime/lib64/bionic/libc.so (__memcpy_aarch64_simd+276) (BuildId: 37f537c2ba9dcbb262a0a68f41a21da4) #01 pc 0000000000026350 /system/lib64/libsfplugin_ccodec_utils.so (android::ImageCopy(C2GraphicView&, unsigned char const*, android::MediaImage2 const*) (.cfi)+2240) (BuildId: a538093d250e5cc55cc6fa850ec43cb4) #02 pc 00000000000c22c8 /system/lib64/libsfplugin_ccodec.so (android::GraphicBlockBuffer::asC2Buffer()+180) (BuildId: 9ad16063071b2e64106291e0c68d1a85) #03 pc 0000000000085c78 /system/lib64/libsfplugin_ccodec.so (android::FlexBuffersImpl::releaseSlot(android::spandroid::MediaCodecBuffer const&, std::__1::shared_ptr<C2Buffer>, bool)+380) (BuildId: 9ad16063071b2e64106291e0c68d1a85) #04 pc 00000000000787a4 /system/lib64/libsfplugin_ccodec.so (android::CCodecBufferChannel::queueInputBufferInternal(android::spandroid::MediaCodecBuffer, std::__1::shared_ptr<C2LinearBlock>, unsigned long)+4888) (BuildId: 9ad16063071b2e64106291e0c68d1a85) #05 pc 000000000007dad4 /system/lib64/libsfplugin_ccodec.so (android::CCodecBufferChannel::requestInitialInputBuffers(std::__1::map<unsigned long, android::spandroid::MediaCodecBuffer, std::__1::less<unsigned long>, std::__1::allocator<std::__1::pair<unsigned long const, android::spandroid::MediaCodecBuffer > > >&&)+1420) (BuildId: 9ad16063071b2e64106291e0c68d1a85) #06 pc 0000000000053694 /system/lib64/libsfplugin_ccodec.so (android::CCodec::start()+1648) (BuildId: 9ad16063071b2e64106291e0c68d1a85) #07 pc 000000000004aa58 /system/lib64/libsfplugin_ccodec.so (android::CCodec::onMessageReceived(android::spandroid::AMessage const&)+1580) (BuildId: 9ad16063071b2e64106291e0c68d1a85) #08 pc 000000000001c720 /system/lib64/libstagefright_foundation.so (android::AHandler::deliverMessage(android::spandroid::AMessage const&)+204) (BuildId: 8452724ba9387b99297617a8eaf138dc) #09 pc 0000000000023adc /system/lib64/libstagefright_foundation.so (android::AMessage::deliver()+176) (BuildId: 8452724ba9387b99297617a8eaf138dc) #10 pc 000000000001dd54 /system/lib64/libstagefright_foundation.so (android::ALooper::loop()+684) (BuildId: 8452724ba9387b99297617a8eaf138dc) #11 pc 00000000000142d4 /system/lib64/libutils.so (android::Thread::_threadLoop(void)+288) (BuildId: a0e0ad47138267db6c479fc556e32d00) #12 pc 00000000000c37b4 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208) (BuildId: 37f537c2ba9dcbb262a0a68f41a21da4) #13 pc 000000000005d084 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68) (BuildId: 37f537c2ba9dcbb262a0a68f41a21da4)

re:Post Agent · Answer

The issue you're experiencing with the Flexcaster app on Samsung Galaxy Z Fold6 5G and Samsung Galaxy S24 Ultra models after a system update appears to be related to a memory access error in the video encoding process. This is indicated by the SIGSEGV (segmentation fault) occurring in the __memcpy_aarch64_simd function, which is part of the system's memory copying operations.

The problem seems to be specific to these particular models and their recent system updates, as it's not occurring on other devices. This suggests that there might be an incompatibility between the Amazon IVS Broadcast SDK (version 1.23.0) and the updated system software or hardware drivers on these specific Samsung models.

The error is happening in the media encoding pipeline, specifically in the process of handling graphic buffers for video encoding. The backtrace shows that the issue occurs during the initialization of input buffers for the media codec.

To address this issue, you could try the following steps:

1. Check if there's a newer version of the Amazon IVS Broadcast SDK available that might have addressed this compatibility issue.

2. Contact Amazon IVS support to report this specific issue with these Samsung models, providing them with the error log and device information.

3. If possible, try rolling back to a previous version of the SDK to see if the issue persists.

4. Implement additional error handling and logging in your app to gather more information about the state of the encoding process when the crash occurs.

5. Consider reaching out to Samsung developer support, as this might be related to changes in their system update that are affecting media encoding on these specific models.

In the meantime, you may need to add a workaround in your app to detect these specific device models and either use an alternative encoding method or disable certain features to prevent the crash.  
**Sources**  
[Known Issues & Workarounds in the IVS Android Broadcast SDK | Real-Time Streaming ​ - Amazon IVS](https://docs.aws.amazon.com/ivs/latest/RealTimeUserGuide/broadcast-android-known-issues.html)  
[Amazon GameLift releases a new version of the server SDKs and game engine plugins | AWS re:Post](https://repost.aws/articles/ARvPLYihj-QuqIbgwnSYd4fw/amazon-gamelift-releases-a-new-version-of-the-server-sdks-and-game-engine-plugins)

SIGSEGV occurs in __memcpy_aarch64_simd after system update on some models (Z Fold6 5G, S24 Ultra)

Relevant content