Closed thatMacAdmin closed 3 years ago
Ah you caught a situation I didn't realise could happen. The crash is a stack overflow. This is caused by the fact that when you call .map
of an already succeeded EventLoopFuture
the closure is called immediately inside the map
function. Your crash involved having 119 calls to map
on already successful EventLoopFutures
which caused a massive recursive function.
I have a fix for this #519. Could you test this and see if it fixes your issue. Thank you
Looks like https://github.com/soto-project/soto/pull/519 resolves this.
Describe the bug Using code like this to resume a multipart upload on failure can cause a crash if there are a large number of resume / retries:
To Reproduce Steps to reproduce the behavior:
Expected behavior SDK should continue to upload parts until complete
Setup (please complete the following information):
Additional context Code fails in this block: Line 684 - S3+multipart_API.swift if let part = parts.first(where: { $0.partNumber == partNumber }) {
ERROR: Thread 106: EXC_BAD_ACCESS (code=2, address=0x30fcfcfd0)
See attached backtrace. backtrace.txt