Comment by Denis S (JIRA)

This bug is especially important when you read from an infinite communication channel like tty, it eats all the memory.

@swift-ci create

Comment by Denis S (JIRA)

Hi! Any update on this? I've just hit it one more time. File reading is a basic operation in OS, it should be safe.

Comment by Andrew Wagner (JIRA)

I am using the following workaround for now:

extension FileHandle { 
    public func safelyReadData(ofLength length: Int) -> Data {
        #if os(Linux)
            var leakingData = self.readData(ofLength: length)
            var data: Data = Data() 
            if leakingData.count > 0 { 
                leakingData.withUnsafeMutableBytes({ (bytes: UnsafeMutablePointer<UInt8>) -> Void in
                    data = Data(bytesNoCopy: bytes, count: leakingData.count, deallocator: .free)
                })
            } 
            return data
        #else
            return self.readData(ofLength: length)
        #endif
    }
}

On Linux it is creating a copy of the data that will actually free the underlying data when deallocated.

Comment by Denis S (JIRA)

Yes, I did similar extension as you with ".free" deallocator. Thanks to Swift's Extension mechanism that allows us to plug leaks and bugs as soon as possible.

Comment by Matt Rajca (JIRA)

#1155