Hi,
I might find the bug of cygwin1.dll (including 3.4.x, 3.5.0 (TEST)).
The following test case (c++ code) causes handle leak.
This issue is reproducible with both g++ and clang++.
However, it does not happen in Linux environment.
So I guess this is the cygwin1.dlll bug.
I looked into this problem a bit, and found number of event handle
increases every loop.
I doubt pthread_mutex_xxx functions.
#include <future>
int func() { return 0; }
int main()
{
for (;;) {
std::future<int> f = std::async(std::launch::async, func);
f.get();
}
return 0;
}
--
Takashi Yano <takashi.y...@nifty.ne.jp>
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
