Closed mannuch closed 1 year ago
However, when running with bind mounts to the local filesystem via
docker run -v "$PWD:/code" -w /code swift:latest swift run -c release
my original application, as well as the reproducer linked above, appear to work.
Thanks for the bug report!
We continued looking into this and strongly suspect that this is a bug with Swift 5.8 and --static-swift-stdlib together with asan
(address sanitizer).
I'll quadruple check some more but that's our strong suspicion so far.
It also does not reproduce on Swift 5.9 and we suspect this might be a fix for it: https://github.com/apple/swift/pull/65254
Ahh okay, got it. Running the Swift 5.8 container without --static-swift-stdlib
seems to be avoiding the issue, so I'll go with that for now!
Thanks for the timely help with this!
Thanks for confirming, I'll close this as I believe this is a static linking issue with concurrency library in general
Hello!
Ran into an issue when running the service in a release configuration on Linux via docker.
After some digging, I believe I've isolated the issue to when the cluster is initialized. I have a reproduction of the issue with a simple main.swift:
When running with Backtrace installed, I get the following:
With the backtrace sending a signal 11, I tried using AddressSanitizer to see if I could get more information, which ended up giving me:
As far as I can tell, the problem only seems to arise when running on Linux with this Dockerfile:
This reproduction, along with the Dockerfile, can be found in this repo, if it helps.
Thanks for all the work on this!