Comments (6)
+1 here
from futurekit.
+1
from futurekit.
+1
from futurekit.
Do you use cancellation? My current theory is maybe a missing need to call lockAndModify somewhere else. Auditing that...
Anyone have a test that can reproduce this?
from futurekit.
Yes we are doing cancellation by calling Promise.completeWithCancel() but never lockAndModify directly. Nevertheless the crash happens inside lockAndModify. Do we need to call lockAndModify directly somewhere?
from futurekit.
I have that crash in QueueBarrierSynchronization.
4 SomeApp 0x00000001012dad04 function signature specialization <Arg[1] = Owned To Guaranteed, Arg[2] = Owned To Guaranteed> of SomeApp.QueueBarrierSynchronization.lockAndModify<A>(waitUntilDone: Swift.Bool, modifyBlock: () -> A, then: (A) -> ()) -> () (Synchronization.swift:236)
5 SomeApp 0x00000001012d6144 SomeApp.QueueBarrierSynchronization.lockAndModify<A>(waitUntilDone: Swift.Bool, modifyBlock: () -> A, then: (A) -> ()) -> () (Synchronization.swift:0)
6 SomeApp 0x00000001012d62f8 protocol witness for SomeApp.SynchronizationProtocol.lockAndModify<A>(waitUntilDone: Swift.Bool, modifyBlock: () -> A1, then: (A1) -> ()) -> () in conformance SomeApp.QueueBarrierSynchronization : SomeApp.SynchronizationProtocol in SomeApp (Synchronization.swift:0)
7 SomeApp 0x00000001012d4fcc (extension in SomeApp):SomeApp.SynchronizationProtocol.lockAndModifySync<A>(() -> A1) -> A1 (Synchronization.swift:82)
8 SomeApp 0x000000010122e8bc function signature specialization <Arg[0] = Owned To Guaranteed, Arg[1] = Owned To Guaranteed, Arg[2] = Owned To Guaranteed> of closure #2 (SomeApp.CancellationToken) -> () in SomeApp.CancellationTokenSource.(_createTrackedToken in _767808852120E968B68EAA4368504F2A)(SomeApp.SynchronizationProtocol) -> SomeApp.CancellationToken (Future.swift:274)
9 SomeApp 0x00000001012528e0 partial apply forwarder for closure #2 (SomeApp.CancellationToken) -> () in SomeApp.CancellationTokenSource.(_createTrackedToken in _767808852120E968B68EAA4368504F2A)(SomeApp.SynchronizationProtocol) -> SomeApp.CancellationToken (Future.swift:0)
10 SomeApp 0x000000010120d178 SomeApp.CancellationToken.__deallocating_deinit (Future.swift:345)
from futurekit.
Related Issues (20)
- Add Linux Support
- Never-ending process when building or archiving. HOT 4
- Cancellation deadlocks HOT 3
- Question: Cancellation of promises HOT 6
- Question: FutureKit 2.0 changes HOT 2
- Better description under title HOT 3
- Swift 3.0 migration HOT 9
- [question] any dedicated way to separate the construction and execution of the promise/future? HOT 1
- [question] flatmap for futures? HOT 2
- make return value of onComplete discardable
- Warnings in the new XCode Version 8.3.2 HOT 2
- Xcode 9.0 support? HOT 1
- Allow futurekit to build via carthage with Xcode 9 HOT 3
- mapAsOptional() has impossible function signature HOT 2
- Combining multiple requests HOT 1
- Build error on Xcode 9 Beta 3 HOT 4
- 3.0.1 release? HOT 2
- Error in completeWithSuccess() on Swift 4 HOT 1
- Documentation link not working
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from futurekit.