-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Threadpool awaitAny()
problem on macOS
#7638
Comments
Hi, I'm trying to do all possible tests, so I spent some time today testing this on Docker and Vagrant, I get the same problem with both on the same machine. I can understand why the problem persist on Docker, but Vagrant suppose to be a full VM. Anyway, I'm happy to do any required tests, and help as much as possible. |
That |
@dom96 I really don't care about the cast since it's just a sample code, even if you remove it the problem remains, it won't work on macOS (I tried) Regarding the cast, to be honest I wish if there is another way to return a result within |
Use a type conversion like so |
Thanks a lot @Araq, I confirm, the code works now. Regarding casting, what you suggest is what I tried originally, but I get this error:
|
That would be another bug. :-) |
Yeah, sorry, and thanks! |
Hi,
I'm having a problem running the following code on macOS 10.13 Intel i7, although, it runs perfectly on a Linux server. I also tried to run it on a different macOS machine with the same problem.
The problem:
The code runs, threads are done with their tasks, but
awaitAny()
doesn't report back all the finished threads/tasks, and the while loop never finishs, sinceawaitAny()
never returns -1.I talked about this problem in Gitter, at the time the problem in the sample code was solved by using
setMinPoolSize()
, but then on a real world program (or extended sample), even settingsetMinPoolSize(MaxThreadPoolSize)
causes the same problem.The text was updated successfully, but these errors were encountered: