- Steps to reproduce the problem

On ADP1 1.5 I noticed Force close/wait messages more frequently than 
before. E.g. after using the search widget on home screen during browser 
startup, or after pressing the camera button during camera initialization.

The close/wait dialog appears. While the dialog is visible the task behind 
starts to run and the timeout condition is cleared.

- What you think the correct behavior should be.

If the application recovers to behave normally the force close/wait dialog 
should disappear without need to confirm the wait button.

The dialog staying visible would only make sense if the application would 
otherwise get into an endless loop of multiple short timeouts. During the 
last two weeks I never had such a case where pressing wait once did not 
help.

So I think the correct behavior would be closing the box from the system.