Summary: they're both called on every request. Not sure if it's a change since this thread was posted but the information here doesn't seem to be correct.

Its neither, its a matter scoping :)

If this is your mod_perl application

sub handler {
   my $app = MyCGIAppSubclass->new;
   $app->run;
}
[download]

cgiapp_init is going to get called with every request, obviously, because you're creating a new object each time -- this is typical Apache::Registry/ModPerl::Registry, running unmodified .cgi's under mod_perl

But if your mod_perl application is

my $app = MyCGIAppSubclass->new;
sub handler {
   $app->run;
}
[download]

Then init/setup is only done once, and only run is done upon every request.

So nothing changed, this are working as designed, as they always have.

See Understanding the application flow of CGI::Application and CGI::Application::Loop

See also the source of CGI::Application::FastCGI

If you want to run CGI::Application as mod_perl handlers as I've shown above with persistent object, you will have to reset query, just like CGI::Application::FastCGI

Ah, it's so blindingly obvious when you point it out, thanks for this. Of course I'm doing exactly what your first example shows, but not for long.

Well, apparently, (I guesstimate) since (some time around) CGI::Application 3.x it is no longer recommended to reuse CGI::Application objects, no longer recommended to call run repeatedly, as Bug #72909 for CGI-Application: persistence issues says CGI::Application is designed to have a new object created on each request. which is an assumption various ::Plugins and extensions make, so its best to play along and not reuse an object and not ->run ->run ->run

You probably discovered this on your own :)