Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of demerphq@gmail.com designates
 209.85.223.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACBZZX75hWM9zZwz7FRSMkh9+O+Hg+1azKQDMNHpSFgi7TFWBg@mail.gmail.com>
References: <005d01cd9d7a$41edb200$c5c91600$@s.profanter.me>
	<5065BDE2.5020104@squeakycode.net>
	<CANgJU+V8jrQkoruxN=bWh=h-6S5MQJoVv6dJjXVgxfEBOhCQpA@mail.gmail.com>
	<000101cd9e32$b12fddb0$138f9910$@s.profanter.me>
	<CACBZZX75hWM9zZwz7FRSMkh9+O+Hg+1azKQDMNHpSFgi7TFWBg@mail.gmail.com>
Date: Tue, 13 Nov 2012 15:48:22 +0100
Message-ID: 
 <CANgJU+XD-AX=4i+QmL4E7c1f-N38DOeoVXSAKnJR2ZMt_D05_A@mail.gmail.com>
Subject: Re: apache2 + mod_perl + Catalyst + Session = Segmentation fault
From: demerphq <demerphq@gmail.com>
To: =?ISO-8859-1?Q?=C6var_Arnfj=F6r=F0_Bjarmason?= <avarab@gmail.com>
Cc: Stefan Profanter <catalyst@s.profanter.me>, modperl@perl.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 13 November 2012 15:23, =C6var Arnfj=F6r=F0 Bjarmason <avarab@gmail.com>=
 wrote:
> On Sat, Sep 29, 2012 at 1:08 PM, Stefan Profanter
> <catalyst@s.profanter.me> wrote:
>>> >
>>> > Looks like you are using Storable to stream out cookies?  Looks like
>>> > something in there is causing Storable to puke.  I see things like
>>> > array_call, store_blessed, store_hash... So I'm guessing your passing
>>> > Storable some kind of object?  Does it have any recursive parts?
>>> >
>>> > I googled "perl storable seg fault" and it looks like people have
>>> > gotten Storable to seg fault before.  I'm not sure if the stack trace
>>> > is reading objects or writing them.  Maybe you can glean from other's
>>> > what makes Storable segfault.
>>> >
>>> > First figure out if its reading or writing that causes the problem,
>>> > then try to figure out what part of the object is so upsetting.
>>> >
>>> >> 3873            return newSVpv(mbase, MBUF_SIZE());
>>> >
>>> >
>>> > Hum... any chance that is really really big?
>>
>> Yes, you were right.
>> I stored a DBIX::ResultSet->single Object in session and it seems this
>> caused the SegFault. Now I stored only the ID instead of whole object an=
d it
>> works.
>>
>>>
>>> Maybe look at Sereal as an alternative to Storable.
>>>
>>> https://github.com/Sereal/Sereal/
>>> http://search.cpan.org/~smueller/Sereal-Decoder/lib/Sereal/Decoder.pm
>>> http://search.cpan.org/~smueller/Sereal-Encoder/lib/Sereal/Encoder.pm
>>>
>>
>> This seems interesting! Do you know by chance how Catalyst::Plugin::Sess=
ion
>> can be set to use Seareal instead of Storable?
>
> I don't have experience with that Catalyst plugin but for e.g.
> Apache::Session we've been using Data::FlexSerializer to migrate away
> from Sereal.

He meant "from Storable (to Sereal)"

Yves

--=20
perl -Mre=3Ddebug -e "/just|another|perl|hacker/"