Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using MonoTouch 4.03. I have some code like this:
ThreadPool.QueueUserWorkItem (delegate
{
Debug.WriteLine("Making connect request");
client.Connect();
});
About one in 10 times it doesn’t get fired. I’m only making very light use of ThreadPool.
NOTE (added 19th July): Currently I have turned LLVM optimisation off and that appears to have cured it.
This is fixed in MonoTouch 4.06 (or possibly the version before – in any case, it’s fixed). I suspect the LLVM optimiser. The MonoTouch release notes show a number of bug fixes in that area.