Re: [swift-corelibs-dev] [swift-users] DateFormatter crash on second usage (new instance) on Linux (swift 3.0.1)

2017-01-25 Thread Philippe Hausler via swift-corelibs-dev
We should run those tests with ASAN, I thought I had fixed that with the Sierra merge. Sent from my iPhone > On Jan 25, 2017, at 6:11 PM, Will Stanton via swift-corelibs-dev > wrote: > > Based on the backtrace, I think the code is running into a memory issue

Re: [swift-corelibs-dev] [swift-users] DateFormatter crash on second usage (new instance) on Linux (swift 3.0.1)

2017-01-25 Thread Will Stanton via swift-corelibs-dev
Based on the backtrace, I think the code is running into a memory issue with Swift Foundation: https://bugs.swift.org/browse/SR-2485 https://bugs.swift.org/browse/SR-2462 I haven’t seen this in a while - are you able to try running on Swift 3.1 or 3.0.2? Your code seems to work on the IBM

Re: [swift-corelibs-dev] Asynchronous Operations

2017-01-25 Thread Ian Partridge via swift-corelibs-dev
Thank you everyone for your comments. Adding willChangeValue(forKey:) and didChangeValue(forKey:) to Operation does solve the problem for me. The Swift 3 code I'm porting from macOS to Linux works correctly when I patch Foundation as Brent suggests. I've opened a PR against