> So when an application has "slowed" can the profiler be run to see what
> routines are being called?   We are getting in a near endless loop and only an
> amazingly fast CPU is keeping us from saying... "an endless loop" and force
> quitting the program.  Can the profiler see that the app is calling a routine
> zillions of times?

I profiled my large-and-problematic app, and the thing it called the most by
far was FN pGBestWindow in this structure, which is the main event loop for
a PG application:

DO
IF FN pGBestWindow THEN WINDOW OUTPUT FN pGBestWindow
HANDLEEVENTS
IF gKissOfDeath THEN GOSUB "PG:Break"
UNTIL 0
if 0 then return

Removing that call entirely helped the problem somewhat, but didn't cure it
entirely. It just took longer for the application to get sluggish.

The rest of the functions high in the profile list were quite ordinary, and
none of them were extraordinarily high, nor did any of them create handles
or dispose of them, so I wonder if this problem is actually code-specific.

Could it have anything to do with the amount of code in the application?
Perhaps something about the way virtual memory is handled by Leopard that's
different than it was in Tiger? And the machine code the FB compiler
produces?

- John