Skip to main content

GUI occassionally freezes

Thread needs solution

Background:
A few days ago I was trying to reproduce a problem I'm having where an FTP backup locks up Windows communication preventing creation of new connections.  I succeeded. Old connections would continue to work, but the ATI FTP client can handle only 2GB transfers and I was trying to back up 1.7GB so it needed to create many, many FTP connections.  So the FTP transfer hung up.

I tried to tell Acronis to stop the transfer.  The GUI accepted the Stop request but then hung up.  Eventually I rebooted out from under ATI.

After the reboot I tried changing backup options but again the GUI hung up.  The backup's Options panel was never displayed.  After the fact I realized that ATI was retrying the backup.  (I let it run and again ran into communication problem. It took 2 hours 30 minutes  the first time but only 1 hour 15 minutes the second time.)  I rebooted again and deleted the backup definition before ATI could attempt a retry.

I don't know how the ATI GUI communicates with background ATI tasks but I would assume that, at the very least, a STOP should be communicated to the backup routine.  When the GUI was hung up after I tried to display the backup's Options, could I have closed the GUI, reopened it, and entered a STOP?  Or once the GUI had a pending request to the backup task (the options display) was it locked but for good?

 

 

0 Users found this helpful

Patrick, I suspect that this is an issue for another Support Case given the lack of information on the design and implementation of ATI available to the public.

There are 'sledge-hammer' methods available to kill off rogue processes, i.e. stopping all associated services and processes, and there is the possibility of a 'deadly embrace' scenario where the 'Cancel' process is holding something that is required by the 'Active' process to be able to obey the cancel request creating a Catch22 situation where neither can complete.

One point to check is that you know what Error Handling options you have set?  Personally I never use these error handling options given the tendency for these to 'run away' and start sending out spam volumes of error emails, especially if left at their default settings.