Closed andrew-xue97 closed 1 year ago
This looks like a stack overflow. If you could post the full stack that'd be great
Thanks for your prompt reply. Unfortunately that's as far as the faulty thread trace goes back.
Here's some extra info in the crash log. Please let me email you the full log if that helps. Thanks! `Thread 7 crashed with ARM Thread State (64-bit): x0: 0x000000016e074428 x1: 0x000000016e074158 x2: 0x0000000000000010 x3: 0x0000000000000000 x4: 0x00000001c588fb8f x5: 0x000000016e0745e0 x6: 0x000000016e0745e0 x7: 0x000000016e0750b4 x8: 0x0000000000000002 x9: 0x0000000000000000 x10: 0x0000000000000001 x11: 0x0000000000000002 x12: 0x0000000000000002 x13: 0x0000000000000078 x14: 0x0000000000000000 x15: 0x000000016e075840 x16: 0x00000001c58178a0 x17: 0x00000001c5817294 x18: 0x0000000000000000 x19: 0x000000000000000a x20: 0x000000016e074316 x21: 0x0000000000000002 x22: 0x0000000000000002 x23: 0x0000000000000002 x24: 0x00000000fffffffd x25: 0x0000000000000080 x26: 0x0000000000000000 x27: 0x000000016e074a64 x28: 0x0000000000000010 fp: 0x000000016e074410 lr: 0xd63d8001c5818c40 sp: 0x000000016e074030 pc: 0x00000001c581f498 cpsr: 0x80001000 far: 0x000000016e073fd0 esr: 0x92000047 (Data Abort) byte write Translation fault
Binary Images:
0x1fadf9000 - 0x1fae2fffb libsystem_kernel.dylib arm64e
I have a possible fix here https://github.com/soto-project/soto-core/pull/538 This should remove the possible chance of a stack overflow when streaming data.
This has now been released in https://github.com/soto-project/soto-core/releases/tag/6.4.2
If you do a swift package update
it should be fixed.
Encountered EXC_BAD_ACCESS during s3FileTransferManager.copy(from: {local_uri}, to: S3File(url: {dest_uri}))
Setup (please complete the following information):
To Reproduce
Additional context The crash was only reported by one user. I was not able to reproduce the crash myself. The Stack trace pointed me to AWSSigner in SOTO, therefore trying to seek help here for some clue. Thanks!