Debian 13 - Apache - FCGI - cgi-mapserver

[Sebastiaan Couwenberg]

On 12/16/25 1:15 PM, Neubauer, Steffen (VermKV) via Pkg-grass-devel wrote:
> this week I performed a server migration from Debian 12 to Debian 13 using the Apache2 and MapServer packages.
> Unfortunately, the MapServer behavior wasn't identical in the same configuration.

You upgraded from 8.0.0 to 8.4.0, that's not unexpected.

Nothing on the migration guide springs out, though:

  https://mapserver.org/MIGRATION_GUIDE.html#mapserver-8-0-to-8-2-migration
  https://mapserver.org/MIGRATION_GUIDE.html#mapserver-8-2-to-8-4-migration

> The single MapServer FCGI processes
> were using 15% of the RAM instead of the previous 1.5%. This caused the VM's RAM to overflow. Even changing the Apache FCGI parameters
> didn't improve the situation. Additionally, the response time of the WMS request was about 200ms slower because
> the FCGI performance couldn't be achieved.

I'm using MapServer via MapScript and the system in question has plenty of RAM, so I don't have any relevant experience.

The response time can be influenced by changes other than MapServer, prime suspect is the data source.

PostGIS and PostgreSQL had many changes between bookworm and trixie as well, the PostGIS selectivity has a regression in 3.5 for example:

  https://lists.osgeo.org/pipermail/postgis-users/2025-September/046864.html
  https://trac.osgeo.org/postgis/ticket/5984

> Is there a known memory leak in the Debian 13 Apache2-FCGI-MapServer configuration?

Nothing in the Debian BTS, you'll have better luck asking other MapServer users:

  https://mapserver.org/community/lists.html#mapserver-users

Kind Regards,

Bas

-- 
  PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1