It can also be bad programming, or a bug in the software.rjent wrote:All I will add to this is that software is software.
Each piece of data (instruction, information, commands, etc) are just microscopic capacitors of some shape or description (many different iterations) holding a on or off state. If only one of those capacitors loses (or changes state), then the whole machine can come crashing down (in a virtual point of view).
A reboot just simply re-establishes the proper state of the "on's" an "off's" in those capacitors. That is never going to change as long as we use the current technology.
Nature of the beast(s)....
I am a courier and the App. that runs on our smart phones, to be dispatched jobs and sign them off, bogs down and then freezes on a fairly regular basis. Re starting the program restores normal operation. With the last, company issued, phones we had it used to crash at the same time every afternoon, now I am using my own, Android, phone and time between crashes is longer and it has a faster response time. There must be part of the code that does not properly release resources after running and eventually there isn't enough left for proper operation. There are other bugs in the code that have been there since before I started with them twelve years ago, so I am not hopeful that the IT department will ever fix it.
