On Fri, Nov 20, 2009 at 1:08 PM, Paul Ramsey wrote:
> A good test case, fully self-contained, is always appreciated. Watch
> out for things like references to templates you don't include or
> font-lists you don't include. After extracting the test case,
> reinstall it and ensure it still shows the
A good test case, fully self-contained, is always appreciated. Watch
out for things like references to templates you don't include or
font-lists you don't include. After extracting the test case,
reinstall it and ensure it still shows the behavior you want.
Thanks,
P.
On Fri, Nov 20, 2009 at 10:
On Fri, Nov 20, 2009 at 12:36 PM, Steve Lime wrote:
> Does 5.6 exhibit the problem? Does a straight CGI call (mode=map)
> exhibit
> the problem? -Steve
>
paalkr 11/20/09 11:37 AM >>>
>
> Hi!
>
> I have discovered a situation where MapServer seems to enter an endless
> loop
> and uses all the
Does 5.6 exhibit the problem? Does a straight CGI call (mode=map)
exhibit
the problem? -Steve
>>> paalkr 11/20/09 11:37 AM >>>
Hi!
I have discovered a situation where MapServer seems to enter an endless
loop
and uses all the CPU power available on a server. I have managed to
track
down the spec
Hi!
I have discovered a situation where MapServer seems to enter an endless loop
and uses all the CPU power available on a server. I have managed to track
down the specific feature in our postgis database that causes MapServer to
hang. A database dump containing only this feature and a working ma