I was wondering if this post was headed in the direction that a user program typically does nothing most of the time, since it does its work and then is paused by kernel or it voluntarily gives execution away to wait for a trap or interrupt. Or it could be waiting for disk access which is like a millennia in terms of CPU time.
I was expecting it to be about GUI programs just waiting for an input.
Because when it hangs, it’s most probably either doing something long, or something that got elongated due to external factors, which ended up being programmed into the GUI thread. So definitely not idling.
I was wondering if this post was headed in the direction that a user program typically does nothing most of the time, since it does its work and then is paused by kernel or it voluntarily gives execution away to wait for a trap or interrupt. Or it could be waiting for disk access which is like a millennia in terms of CPU time.
I was expecting it to be about GUI programs just waiting for an input.
Because when it hangs, it’s most probably either doing something long, or something that got elongated due to external factors, which ended up being programmed into the GUI thread. So definitely not idling.