Code profiler doesn't always give a report?

General
1

I had trouble getting the profiler to work.
I’d enabled Code Profiler in the project, Ran the project and then in the ide pressed the stop button.
That used to bring up a profiler report. It isn’t anymore for some reason.

I’m using Version 2016 Release 2 Pro.
(License has now expired for updates I guess)

2

As far as I know, that would never bring up the Profile. You have to let the app run until it quits naturally.

3

[quote=345675:@Brian O’Brien]I had trouble getting the profiler to work.
I’d enabled Code Profiler in the project, Ran the project and then in the ide pressed the stop button.
That used to bring up a profiler report.
[/quote]
Nope
Never did
The app has to be QUIT before you get a report

4

It’s a web app. When I close the last page I thought it was suppose to exit on its own in the debugger.

5

it will - eventually
but if you kill it using the stop button you wont get a report
that’s always been true
its just the way the profiler works

you could put a button on you web app or a special url that QUITS the app
then you dont have to wait for it to eventually time out

6

I don’t get it… it was working and now it has stopped working.

7

I think your misremembering things

Using “QUIT” in the IDE is like using “FORCE QUIT” to quit an app
Stuff that normally happens when the app quits doesn’t because it never runs that code

The profiler is one of these things that runs normally when you apps quits normally
If you “quit” the app by running a “quit” statement or letting it time out on its own then the profiler will do its thing
Otherwise it wont
It literally cant do otherwise

AND FWIW I just crafted a tiny app in 2016r3 and did both
Using the quit button in the IDE I do not get a profile report
Closing the last browser tab & waiting a moment I do
Or in the method I was interested in I put a “quit” at the end and I also get a profile report
Exactly as I expected in all cases