Tom Schindl wrote:
> As a sidenote often it is not really desired/dangerous to run image
> creation as a mod_perl handler because of the nature of perl, memory
> allocated once is never freed until the process shutdowns or is killed
> (by your Apache::SizeLimit handler).
>
> I'm not familiar with
As a sidenote often it is not really desired/dangerous to run image
creation as a mod_perl handler because of the nature of perl, memory
allocated once is never freed until the process shutdowns or is killed
(by your Apache::SizeLimit handler).
I'm not familiar with fastcgi but you should make sur
Christopher H. Laco wrote:
> That's in on the nose. Text::Textile uses Image::Size, which uses
> Image::Magick. Any incantation of pre loading this modules makes apache
> core.
>
> The funny part is, it only segfaults the main httpd process. apachectl
> start yields a core dump, but the child pro
BjXrn Erik Jacobsen wrote:
> At 05:04 23.03.2006, you wrote:
>> I'm working on a site running under Catalyst under ModPerl
>> 2.0.2/Apache2.0.55.
>>
>> As soon as I tried loading Text::Textile in any way, apache segfaults,
>> even when just doing apachectl configtest.
>>
>> Text::Textile is a pure
At 05:04 23.03.2006, you wrote:
>
> I'm working on a site running under Catalyst under ModPerl
> 2.0.2/Apache2.0.55.
>
> As soon as I tried loading Text::Textile in any way, apache segfaults,
> even when just doing apachectl configtest.
>
> Text::Textile is a pure perl module, and uses Exporter. No
Christopher H. Laco wrote:
> I'm working on a site running under Catalyst under ModPerl
> 2.0.2/Apache2.0.55.
>
> As soon as I tried loading Text::Textile in any way, apache segfaults,
> even when just doing apachectl configtest.
>
> Text::Textile is a pure perl module, and uses Exporter. Nothing
