Is there any way to find out why code profiling doesn’t do any result on my main project? Smaller projects work fine. The important project doesn’t give me a profiling result. I can see the quit menu handler executing. And then nothing.
Xojo 2020r2.1 on High Sierra
Two things that I am aware of which can prevent it.
If the application is in the App Sandbox.
If you’re using the terminate declare to quit your application (probably called terminate in MBS too).
Beatrix_Willius:
And then nothing.
All the time…
No sandbox, no terminate declare.
<https://xojo.com/issue/64149 >: Do profiling independently on how app quits
<https://xojo.com/issue/64150 >: When profiling if no profile data can be collected give information why
This is probably doing to be implemented in the next decade. Told the user to install XCode.
You don’t have a call to StopProfiling in your app anywhere do you?
That was the first thing I checked.
Is it possible your app is actually crashing at quit, but the quit is masking it?
1 Like
Got it. Some users had problems with quitting and for those I had added a terminate. This interfered with profiling.
2 Likes
Arnaud_N
(Arnaud N)
March 25, 2021, 4:46pm
11
For the sake of completeness, Remote Debugging can also be a reason.
Isn’t it possible to add a warning at IDE run time, something like:
"Your project use remote debugging, Exterminate, etc…”. “Code profiling do not works under these conditions…”
before running the application…
and with two buttons: “Cancel” and “Continue without Code Profiling”…