Jakob Mittelberger
Jakob Mittelberger
I did some further digging and found out, that: ```swift func getAllHandler(_ req: Request) throws -> EventLoopFuture { var elaborations: [Elaboration] = [] for _ in 0...60000{ let elaboration =...
I created a small test project to reproduce this issue: https://github.com/gipfelen/vaporLinuxLeak simply call "docker-compose-up" and try to access http://localhost:8081/hello once and you should get a "leak" of 700MB
You can execute the program in macOS, and you will see, that the memory will be released after the api call.
It was the RELEASE binary.
@Joannis RELEASE as in `swift build -c release` @fouadhatem Yes, I saw it, but it has nothing to do with the database. Thus it has a different origin.
I changed my https://github.com/gipfelen/vaporLinuxLeak such that it uses jemalloc instead of malloc. But after a single call of http://localhost:8080/hello it uses more than 800MB of RAM, and it doesn't get...
@Lukasa currently I'm testing it with Docker on macOS, where the VM is limited to 2GB of RAM. The CPU usage of the container is below 0.0% thus it also...
Your fix works perfectly, but I'm unable to get the microphone working with audio id 2. Any suggestions?
I fixed the issue by directly using prerelease lilu/audioALC kext files! (now it works with audio-id 1 injected)