Cannot get full performance data due to fixed 3 min timeout

[ppiasek]

I'm trying to get CPU Profiler data, but apparently its size is quite big and appium times out, when extracting it. I've checked the code and found that there is a fixed stop timeout set to 3 minutes.

https://github.com/appium/appium-xcuitest-driver/blob/master/lib/commands/performance.ts#L18

My suggestion is to either add ability to extend that timeout in settings / capabilities or as an argument to mobile: stopPerfRecord method.

Server logs:

2026-07-29 14:41:39:230 [55d821fb][HTTP] --> POST /session/55d821fb-62dc-4998-8c2a-c4e558ab672a/execute/sync {"script":"mobile: stopPerfRecord","args":[{"profileName":"CPU Profiler"}]}
2026-07-29 14:41:39:230 [55d821fb][XCUITestDriver@310f] Calling AppiumDriver.execute() with args: ["mobile: stopPerfRecord",[{"profileName":"CPU Profiler"}],"55d821fb-62dc-4998-8c2a-c4e558ab672a"]
2026-07-29 14:41:39:230 [55d821fb][XCUITestDriver@310f] Executing command 'execute'
2026-07-29 14:41:39:520 [55d821fb][CPU Pro...@00008120] [xctrace] Stopping recording...
2026-07-29 14:42:09:221 [55d821fb][XCUITestDriver@310f] RemoteXPC upstream socket disconnected (local 50610 -> device 50610)
2026-07-29 14:42:09:226 [XCUITestDriver@310f] RemoteXPC downstream socket disconnected (local 50610 -> device 50610)
2026-07-29 14:44:39:240 [55d821fb][CPU Pro...@00008120] Performance recording has failed to exit after 180000ms

[KazuCocoa]

Do you mean because the running profile command took long to end with SIGINT, so 3 minutes didn't sufficient time to end the process...? How long does it usually take in your case?

[ppiasek]

Hard to say, but if I run recording directly from xcode, the trace file was roughly 600MB in size for all processes and couple of minutes on recording. I believe the transfer is slow, at least when saving to a file locally.

When I tried stopping Activity Monitor, it also timed out but I managed to get 1,5MB of file. Network though finished fine with ~250KB of size.

If the performance recording is using xcode instruments, why it cannot save the recording directly into the controlling machine filesystem?

[KazuCocoa]

The actual command is:

appium-xcuitest-driver/lib/commands/performance.ts

Lines 103 to 127 in 4979077

	if (toolName === XCTRACE) {
	args.push(
	XCTRACE,
	'record',
	'--device',
	this._udid,
	'--template',
	this._profileName,
	'--output',
	this._reportPath,
	'--time-limit',
	`${this._timeout}ms`,
	);
	if (this._pid) {
	args.push('--attach', `${this._pid}`);
	} else {
	args.push('--all-processes');
	}
	} else {
	// https://help.apple.com/instruments/mac/current/#/devb14ffaa5
	args.push('-w', this._udid, '-t', this._profileName, '-D', this._reportPath, '-l', `${this._timeout}`);
	if (this._pid) {
	args.push('-p', `${this._pid}`);
	}
	}

so you can check if the file was properly created or not. Based on the description, I guess the xcrun command or instrument command ended with non-zero even if they ended properly (I guess) - then, the issue is the underlying xcrun command side potentially.

Current response design is to follow WebDriver Protocol.

Could you share the full appium log as well (as GIST)?