State:Closed|icon_bug|icon_katana|database:public|Resolution:Fixed|BugID:233796|TargetRelease:2.5v4|
Problem summary:
No profiling information is written when using `--force-profile`in batch mode.
This is a regression between 2.5v1.001570b (3rd of 5 betas of 2.5v1) and 2.5v1.001600b (4th beta)
Steps to reproduce:
Expected behaviour:
Files are written to /tmp/prof
Actual behaviour:
No files are written to /tmp/prof
Workaround:
Profiling still works in UI mode with `StartProfilingSession()` and `EndProfilingSession()`
Reproduced versions/platforms:
Customer version/platform:
2.5v3
We're sorry to hear that
Please tell us why