Opened 8 years ago
Closed 8 years ago
#10968 closed Bugs (fixed)
The futures returned by async() and future::then() are not blocking
| Reported by: | viboes | Owned by: | viboes |
|---|---|---|---|
| Milestone: | Boost 1.58.0 | Component: | thread |
| Version: | Boost 1.57.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
Instead of blocking on the future destructor they block on the destructor of the shared state.
Change History (6)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 8 years ago
The issues with shared_future::then have been solved. However the fallback_to test fails often.
comment:4 by , 8 years ago
| Milestone: | To Be Determined → Boost 1.58.0 |
|---|
I have reached to fix the remaining issues. The future shared_state was destroyed while been locked. In order to avoid the destruction a centinel has been added.
comment:5 by , 8 years ago
comment:6 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
This branch contains fixes https://github.com/boostorg/thread/tree/fix/blocking_future.
I have found a lot of issues on the current implementation and most of them are fixed now (well at least I think so), however I have yet some issues with shared_future::then.