Avast.setup hangs on Settings - Update (Basic) Details

[system]

Upon going through the settings, the setup utility consistenty and constantly hangs on the Update (Basic) screen when Details is selected.

Going into the Task Manager, I notice the memory usage for Avast.setup increasing by the second and if I try to end the task via the Task Manager, it tells me that I cannot do it. It will eventually hang if I try to close it via the red and it doesn’t close, causing two instances of dumpprep.exe to be created which ultimately sends the error report (in this case, two reports) to Microsoft.

This happens all the time.

There appears to be a problem with this. I don’t know if it is a memory leak in Avast.setup, but someone should really take a look at it. The only thing I am trying to change on that “Details” screen is to simply display the icon when it is updating.

System specifications:

Windows XP Home - Service Pack 3
CPU: AMD K6-2 500 MHz
Memory: 768 Mb

UPDATE: It does not hang when changing the settings in Safe Mode.

[igor0]

How long did you wait before calling the avast.setup process frozen? How big its memory usage was?
Can you post the few last pages of \Setup\Setup.log, taken right after the problem has been simulated?
Thanks.

[Lisandro]

Does the freeze occur if you’re not updating, i.e., if avast.setup is not running?

[system]

Yes, it was launched when it was not updating.

I waited a good one minute before deciding it hung after I clicked the referenced selection, the memory usage for Avast.setup per the Task Manager started at 56 Mb and by the time I was successful in getting the Task Manager to “End Task” it, it was up to 75 Mb.

No log is available as I decided to uninstall it, as I am researching further system problems.

[Lisandro]

@epp post:4

Yes, it was launched when it was not updating.

I waited a good one minute before deciding it hung after I clicked the referenced selection, the memory usage for Avast.setup per the Task Manager started at 56 Mb and by the time I was successful in getting the Task Manager to “End Task” it, it was up to 75 Mb.

If avast.setup is running, then an update is being performed. So, the update is what is hanging :

[system]

@Tech post:5

@epp post:4

Yes, it was launched when it was not updating.

I waited a good one minute before deciding it hung after I clicked the referenced selection, the memory usage for Avast.setup per the Task Manager started at 56 Mb and by the time I was successful in getting the Task Manager to “End Task” it, it was up to 75 Mb.

If avast.setup is running, then an update is being performed. So, the update is what is hanging :

Why would avast.update continually increase memory usage? I resolved a system problem (memory-related) and reinstalled Avast. avast.setup is currently running in the background, according to the Task Manager ™, it is using roughly one-third of the CPU power, yet the amount of memory it is using, increases at each TM screen refresh.

UPDATE: I let the computer sit there for an hour, during this time, avast.cetup completed updating and once I went into that Settings screen, it did not hang.

The lack of the (i) icon appearing is the only outstanding issue (in another thread).

[Lisandro]

The update processing run at low priority, using less CPU resources. There’s a code in the updater that limits the CPU usage to 30% maximum, i.e., when the update is taking place, the updating process take at most 30% of the CPU (or, if you’re using a dual core machine, 15%).