New issue
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
Crash CompositeEventMonitor #3635
Comments
I'm getting the same thing but I'm unable to recreate it. Were you able to figure this one out? |
It really seems like some sort of underlying Swift issue. Building with the latest Xcode may make it go away, or, if you aren't using the Session(..., eventMonitors: []) This will ensure that the |
@jshier I'm witnessing a similar crash in the |
@ejensen Can you post the textual crash log that Crashlytics has? At least the call stack of the crashing thread would be helpful. But you're right, I misremembered the |
Stack Trace
The |
Yeah, I'm not sure I can ship such a change. Ultimately the issue is I don't understand the cause of the crash. Iteration of a constant array should't cause any issues, even from multiple queues, as there's no mutation. All I can think is that the values passed into the |
I have another problem that also needs to avoid the I'm using Alamofire in a little corner of a larger Vapor project (using AsyncHTTPClient in most cases...). Since Vapor blocks the main thread I try to avoid Alamofire scheduling/dispatching anything on it. Currently, there is no way to disable the
Alamofire/Source/EventMonitor.swift Lines 223 to 225 in 81a2972
It would be helpful if the |
What did you do?
We update using alamofire 5.4.4 or version 5.6.1
What did you expect to happen?
Not crash
What happened instead?
to many crash in CompositeEventMonitor
Alamofire Environment
**Alamofire Version: 5.4.4 or version 5.6.1
Dependency Manager:
**Xcode Version:13.4.1
Swift Version:
Platform(s) Running Alamofire:
macOS Version Running Xcode:
The text was updated successfully, but these errors were encountered: