IA update agent bug
Posted: Wed May 18, 2016 11:19 am
When I installed IA X4, I selected the option to let it check for updates automatically. I have been using that option before, and it was working fine. It offers to do that at 3 am, which is ok with me. My work PC is locked (Win+L) during the night, but the IA updater can log in on its own.
This morning, when I logged in, I found it in this state: my desktop was filled with small popups from "myahew" saying "Not enough timers available". When I dismissed all of those, there was a bunch of dialogs asking "Are you sure you want to cancel? Yes No". When I closed all those (clicking No), I discovered the IA setup already running, which then displayed the error message that it cannot complete because "Not enough timers available" and exited.
It looks like the IA update agent checked for updates during the night, found a new update and ran the installer without even asking me. And then kept asking something on a timer until it ran out of system timer resources.
This is not good. Offering to install a new update is Ok, but it should never run the installer without my permission. And if the user does not respond, popping endless dialogs and running out of resources is obviously a bug.
This morning, when I logged in, I found it in this state: my desktop was filled with small popups from "myahew" saying "Not enough timers available". When I dismissed all of those, there was a bunch of dialogs asking "Are you sure you want to cancel? Yes No". When I closed all those (clicking No), I discovered the IA setup already running, which then displayed the error message that it cannot complete because "Not enough timers available" and exited.
It looks like the IA update agent checked for updates during the night, found a new update and ran the installer without even asking me. And then kept asking something on a timer until it ran out of system timer resources.
This is not good. Offering to install a new update is Ok, but it should never run the installer without my permission. And if the user does not respond, popping endless dialogs and running out of resources is obviously a bug.