Open Radar

 
Area:
Time Machine

Summary:
PLEASE NOTE: This is not a bug with Time Machine data or backup behavior, but a bug with the app itself and it's behavior responding to an AppleScript activation. Please do me the favor of trying the simple AppleScript described below before asking me to create a hundreds-of-megabytes large system profile.

Bug: Time Machine app doesn't respond to activation event, causing the sending app/process to hang. In an app like my FastScripts, because AppleScripts are run on the main thread, this causes the app to hang. In an app like Script Editor where the app is run on a thread, it causes the script window to become unusable.

Steps to Reproduce:
1. Open Script Editor
2. Paste in the following script:

tell application "Time Machine" to activate

3. Run.

Expected Results:
Time Machine is activated for the current app, and the script completes running.

Actual Results:
The script keeps running until it finally times out.

The problem can be ameliorated by adding an explicit, shorter timeout around the call:

try
	with timeout of 0.1 seconds
		tell application "Time Machine" to activate
	end timeout
end try

Whatever TimeMachine.app is doing in response to the activation event, it should cede control back to the calling app by responding appropriately to the event.


Version:
10.12.3 (16D32)

Notes:


Configuration:


Attachments: