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 dont understand why Threads have to ‘sleep’ if there is no event in the Application Run Loop. Does this save energy, or memory, or what else?
When there comes in an event from an source input, then it would wake up that Thread again to handle this event. After that, it would sleep again, for the case that there is no more event in the queue waiting to be processed.
Does someone have a good explanation for this sleeping issue?
It’s not an issue. It’s a good thing. What else would the main thread be doing? It shouldn’t be processing long-running tasks – that would reduce the ‘snappiness’ of the UI when a UI event comes in.
It shouldn’t be tight-looping until an event comes in – that would take up processor time which can otherwise be sensibly used by other applications.
Sleeping (or rather waiting) is exactly what you want it to do – so it can wake up as soon as it has useful work to do, but otherwise doesn’t impact the system.