Skip Menu |
 

This queue is for tickets about the MooseX-Storage CPAN distribution.

Report information
The Basics
Id: 99068
Status: open
Priority: 0/
Queue: MooseX-Storage

People
Owner: Nobody in particular
Requestors: chris [...] lokku.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



MIME-Version: 1.0
X-Spam-Status: No, score=-2.598 tagged_above=-99.9 required=10 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
X-Spam-Flag: NO
Content-Type: multipart/alternative; boundary="089e0111d1be9417ab0503ae6c5c"
Message-ID: <CAPPXNB6whAHp73Vt27vY+ELgi6nPVM1a0gn5sswvHH6WywRFpw [...] mail.gmail.com>
X-Received: by 10.50.43.193 with SMTP id y1mr17432547igl.32.1411422564388; Mon, 22 Sep 2014 14:49:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
X-Spam-Score: -2.598
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id D9A2D2404D1 for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 17:49:32 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZG-pKDsdWGn7 for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 17:49:31 -0400 (EDT)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id 6DB0A2403A6 for <bug-MooseX-Storage [...] rt.cpan.org>; Mon, 22 Sep 2014 17:49:31 -0400 (EDT)
Received: (qmail 25753 invoked by alias); 22 Sep 2014 21:49:30 -0000
Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Mon, 22 Sep 2014 14:49:28 -0700
Received: by mail-ie0-f170.google.com with SMTP id x19so5469128ier.15 for <bug-MooseX-Storage [...] rt.cpan.org>; Mon, 22 Sep 2014 14:49:24 -0700 (PDT)
Received: by 10.107.160.17 with HTTP; Mon, 22 Sep 2014 14:49:24 -0700 (PDT)
Authentication-Results: hipster.bestpractical.com (amavisd-new); dkim=pass header.i= [...] gmail.com
Delivered-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
Subject: Memory Leak with MooseX::Storage
Return-Path: <chris.lokku [...] gmail.com>
X-RT-Mail-Extension: moosex-storage
X-Original-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
X-Spam-Check-BY: la.mx.develooper.com
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=jVfPXR81l+/CKiPf5P6/X9+TSHO6Tslh/mXb78zlUlw=; b=daOUZ/3+six46tH/pihFBVLw0Zj4WH6P4/WQ8XGqRask0eqFbS+k6Tskf/gB6q5ckg wM0han7mKaxrLezHgkPlPXeqa4iHDUbzCWplNiBOwLWBcITlvLiRq6m6O3TzCjoynzpq fKcNAd5gSnRLyQOD2bh+bweXWH1Th05LQ1EKdWemS4AqwfCz9V96XAD5/d7sypGe21hC 9+ITo7WrNCDCwPsJ50cQEDZoRrwV5AcbEwuH79d5zJao7jktGuA76iRUu6eaq9HfUYEl waU/RLqnSKq35/VGncEoPJ8kiNm1vA0vm0sI9TetqAK7LUjkB3GR1fUkVHtVeVq7NCby AGqA==
X-Google-Sender-Auth: l-blmWNTsTVyTW9dlPPGwq0Fn0E
Date: Mon, 22 Sep 2014 22:49:24 +0100
Sender: chris.lokku [...] gmail.com
X-Spam-Level:
To: bug-MooseX-Storage [...] rt.cpan.org
From: Chris Hughes <chris [...] lokku.com>
X-RT-Interface: Email
Content-Length: 0
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Content-Length: 505
Download (untitled) / with headers
text/plain 505b
I'm seeing memory issues in long lived processes using MooseX::Storage. The simple example below seems to reproduce the issue (testing with perl 5.18.2, MooseX::Storage 0.46 and 0.47). The process continually grows by ~10Mb every 100,000 or so iterations. package Obj; use Moose; use MooseX::Storage; with Storage('format' => 'JSON'); has 'string', ( isa => 'Str', is => 'rw' ); __PACKAGE__->meta->make_immutable; 1; my $Obj = Obj->new({ string => 'a string' }); while (1) { $Obj->pack(); }
content-type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Content-Length: 882
X-Sa-Exim-Connect-Ip: 69.50.167.197
MIME-Version: 1.0
X-Spam-Status: No, score=-4.449 tagged_above=-99.9 required=10 tests=[AWL=1.451, BAYES_00=-1.9, FROM_OUR_RT=-4] autolearn=ham
In-Reply-To: <rt-4.0.18-4248-1411422573-1742.99068-4-0 [...] rt.cpan.org>
Content-Disposition: inline
X-Spam-Flag: NO
X-RT-Interface: API
References: <RT-Ticket-99068 [...] rt.cpan.org> <CAPPXNB6whAHp73Vt27vY+ELgi6nPVM1a0gn5sswvHH6WywRFpw [...] mail.gmail.com> <rt-4.0.18-4248-1411422573-1742.99068-4-0 [...] rt.cpan.org>
X-Acl-Warn: !authenticated = *
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
Message-ID: <20140922221005.GS79240 [...] tequila>
content-type: text/plain; charset="utf-8"
X-Spam-Score-Int: 0
X-RT-Original-Encoding: utf-8
X-Spam-Score: -4.449
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id 4D6AD2404D1 for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 18:10:17 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ObQaU8Zw91K for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 18:10:16 -0400 (EDT)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id C1C862403A6 for <bug-MooseX-Storage [...] rt.cpan.org>; Mon, 22 Sep 2014 18:10:15 -0400 (EDT)
Received: (qmail 27042 invoked by alias); 22 Sep 2014 22:10:14 -0000
Received: from ns2.lightspeed.ca (HELO www.lightspeed.ca) (206.12.82.4) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Mon, 22 Sep 2014 15:10:12 -0700
Received: from 69-50-167-197.westerncable.ca ([69.50.167.197] helo=etheridge.ca) by www.lightspeed.ca with esmtp (Exim 4.80) (envelope-from <ether [...] cpan.org>) id 1XWBo6-0001ax-2d for bug-MooseX-Storage [...] rt.cpan.org; Mon, 22 Sep 2014 15:10:06 -0700
Delivered-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
Subject: Re: [rt.cpan.org #99068] Memory Leak with MooseX::Storage
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Sa-Exim-Mail-From: ether [...] cpan.org
Return-Path: <ether [...] cpan.org>
X-Spam-Check-BY: la.mx.develooper.com
X-Original-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
X-RT-Mail-Extension: moosex-storage
Date: Mon, 22 Sep 2014 15:10:05 -0700
X-Sa-Exim-Scanned: No (on www.lightspeed.ca); SAEximRunCond expanded to false
X-Spam-Level:
X-Spam-Bar: /
To: Chris Hughes via RT <bug-MooseX-Storage [...] rt.cpan.org>
Mail-Followup-To: Chris Hughes via RT <bug-MooseX-Storage [...] rt.cpan.org>
From: Karen Etheridge <ether [...] cpan.org>
RT-Message-ID: <rt-4.0.18-857-1411423818-930.99068-0-0 [...] rt.cpan.org>
Content-Length: 469
Download (untitled) / with headers
text/plain 469b
On Mon, Sep 22, 2014 at 05:49:34PM -0400, Chris Hughes via RT wrote: Show quoted text
> I'm seeing memory issues in long lived processes using MooseX::Storage. > The simple example below seems to reproduce the issue (testing with perl > 5.18.2, MooseX::Storage 0.46 and 0.47). The process continually grows by > ~10Mb every 100,000 or so iterations.
Could you tell me your installed versions, if any, of: Moose JSON::Any Cpanel::JSON::XS JSON::XS JSON::PP JSON JSON::DWIW thanks!
MIME-Version: 1.0
X-Spam-Status: No, score=-4.598 tagged_above=-99.9 required=10 tests=[AWL=2.000, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, FROM_OUR_RT=-4, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
In-Reply-To: <rt-4.0.18-857-1411423818-257.99068-6-0 [...] rt.cpan.org>
X-Spam-Flag: NO
X-RT-Interface: API
References: <RT-Ticket-99068 [...] rt.cpan.org> <CAPPXNB6whAHp73Vt27vY+ELgi6nPVM1a0gn5sswvHH6WywRFpw [...] mail.gmail.com> <rt-4.0.18-4248-1411422573-1742.99068-4-0 [...] rt.cpan.org> <20140922221005.GS79240 [...] tequila> <rt-4.0.18-857-1411423818-257.99068-6-0 [...] rt.cpan.org>
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
X-Received: by 10.50.73.72 with SMTP id j8mr15924038igv.32.1411425030695; Mon, 22 Sep 2014 15:30:30 -0700 (PDT)
Message-ID: <CAPPXNB6F7UZ5Z66mTCeWmcTw0pw9NArGTO37g-RXc8Rh-vx9Qg [...] mail.gmail.com>
Content-Type: multipart/alternative; boundary="089e013a240c94eff30503aeff43"
X-Spam-Score: -4.598
Authentication-Results: hipster.bestpractical.com (amavisd-new); dkim=pass header.i= [...] gmail.com
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id 6EC542404AA for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 18:30:40 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B+x9cOMGnS08 for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 18:30:38 -0400 (EDT)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id A1CFF2403A6 for <bug-MooseX-Storage [...] rt.cpan.org>; Mon, 22 Sep 2014 18:30:37 -0400 (EDT)
Received: (qmail 28352 invoked by alias); 22 Sep 2014 22:30:36 -0000
Received: from mail-ig0-f179.google.com (HELO mail-ig0-f179.google.com) (209.85.213.179) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Mon, 22 Sep 2014 15:30:34 -0700
Received: by mail-ig0-f179.google.com with SMTP id l13so3618299iga.0 for <bug-MooseX-Storage [...] rt.cpan.org>; Mon, 22 Sep 2014 15:30:30 -0700 (PDT)
Received: by 10.107.160.17 with HTTP; Mon, 22 Sep 2014 15:30:30 -0700 (PDT)
Delivered-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
Subject: Re: [rt.cpan.org #99068] Memory Leak with MooseX::Storage
Return-Path: <chris.lokku [...] gmail.com>
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=cM1iJK3rffDn4t7BE3A/Xyxb1Lhh8QdeVwv6C4eddys=; b=obu8EeFcp84bdGlhhbsvjOG/MgMuu6Oz0hHbFlXWgUtBfEDwl2HPDVUUc2GaG1qqHi rKaDcmzqmMcId3JoJNvZmdp5PViIpgMgkZUQVJoF0I5d1aY8PDjcXHDB27ALpIBybfvZ 11568/G0rBnaGHhnRFc3/5xoAkVWFw7n2OfQylNtKpzTacun7P075mKLsIDp82qHuCNU OD/SiQldCYlSMEZb1cXJcorEoe8Kkb1yBUCjSYiLhPgRXG9I1Md/CQlTyNKlD7weT8Ft GlfJn9TaL8B6pUixotUu+G5uOSFhN045WBlN6Eonb4s0PgZXKcxWpcWl5H4QngSED4vX o8jQ==
X-Spam-Check-BY: la.mx.develooper.com
X-Original-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
X-RT-Mail-Extension: moosex-storage
X-Google-Sender-Auth: 5RDXH1xAbrhr_G-Px0m-6yYlf34
Sender: chris.lokku [...] gmail.com
Date: Mon, 22 Sep 2014 23:30:30 +0100
X-Spam-Level:
To: bug-MooseX-Storage [...] rt.cpan.org
From: Chris Hughes <chris [...] lokku.com>
RT-Message-ID: <rt-4.0.18-32262-1411425041-910.99068-0-0 [...] rt.cpan.org>
Content-Length: 0
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Content-Length: 766
Download (untitled) / with headers
text/plain 766b
Sure - hope this helps: Moose - 2.1210 JSON::Any - 1.34 JSON::XS - 3.01 JSON::PP - 2.27202 JSON - 2.90 On 22 September 2014 23:10, Karen Etheridge via RT < bug-MooseX-Storage@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=99068 > > > On Mon, Sep 22, 2014 at 05:49:34PM -0400, Chris Hughes via RT wrote:
> > I'm seeing memory issues in long lived processes using MooseX::Storage. > > The simple example below seems to reproduce the issue (testing with perl > > 5.18.2, MooseX::Storage 0.46 and 0.47). The process continually grows by > > ~10Mb every 100,000 or so iterations.
> > Could you tell me your installed versions, if any, of: > > Moose > JSON::Any > Cpanel::JSON::XS > JSON::XS > JSON::PP > JSON > JSON::DWIW > > thanks! > > >
content-type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Content-Length: 1365
X-Sa-Exim-Connect-Ip: 69.50.167.197
MIME-Version: 1.0
X-Spam-Status: No, score=-4.462 tagged_above=-99.9 required=10 tests=[AWL=1.438, BAYES_00=-1.9, FROM_OUR_RT=-4] autolearn=ham
In-Reply-To: <rt-4.0.18-32262-1411425041-489.99068-5-0 [...] rt.cpan.org>
Content-Disposition: inline
X-Spam-Flag: NO
X-RT-Interface: API
References: <RT-Ticket-99068 [...] rt.cpan.org> <CAPPXNB6whAHp73Vt27vY+ELgi6nPVM1a0gn5sswvHH6WywRFpw [...] mail.gmail.com> <rt-4.0.18-4248-1411422573-1742.99068-4-0 [...] rt.cpan.org> <20140922221005.GS79240 [...] tequila> <rt-4.0.18-857-1411423818-257.99068-6-0 [...] rt.cpan.org> <CAPPXNB6F7UZ5Z66mTCeWmcTw0pw9NArGTO37g-RXc8Rh-vx9Qg [...] mail.gmail.com> <rt-4.0.18-32262-1411425041-489.99068-5-0 [...] rt.cpan.org>
X-Acl-Warn: !authenticated = *
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
Message-ID: <20140923003441.GU79240 [...] tequila>
content-type: text/plain; charset="utf-8"
X-Spam-Score-Int: 0
X-RT-Original-Encoding: utf-8
X-Spam-Score: -4.462
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id A4E062404E1 for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 20:34:57 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCAUGg2YRoHy for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 20:34:55 -0400 (EDT)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id 8F6072403A6 for <bug-MooseX-Storage [...] rt.cpan.org>; Mon, 22 Sep 2014 20:34:55 -0400 (EDT)
Received: (qmail 5391 invoked by alias); 23 Sep 2014 00:34:54 -0000
Received: from ns2.lightspeed.ca (HELO www.lightspeed.ca) (206.12.82.4) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Mon, 22 Sep 2014 17:34:52 -0700
Received: from 69-50-167-197.westerncable.ca ([69.50.167.197] helo=etheridge.ca) by www.lightspeed.ca with esmtp (Exim 4.80) (envelope-from <ether [...] cpan.org>) id 1XWE41-0005IF-Qp for bug-MooseX-Storage [...] rt.cpan.org; Mon, 22 Sep 2014 17:34:46 -0700
Delivered-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
Subject: Re: [rt.cpan.org #99068] Memory Leak with MooseX::Storage
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Sa-Exim-Mail-From: ether [...] cpan.org
Return-Path: <ether [...] cpan.org>
X-Spam-Check-BY: la.mx.develooper.com
X-Original-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
X-RT-Mail-Extension: moosex-storage
Date: Mon, 22 Sep 2014 17:34:41 -0700
X-Sa-Exim-Scanned: No (on www.lightspeed.ca); SAEximRunCond expanded to false
X-Spam-Level:
X-Spam-Bar: /
To: Chris Hughes via RT <bug-MooseX-Storage [...] rt.cpan.org>
Mail-Followup-To: Chris Hughes via RT <bug-MooseX-Storage [...] rt.cpan.org>
From: Karen Etheridge <ether [...] cpan.org>
RT-Message-ID: <rt-4.0.18-10676-1411432498-1688.99068-0-0 [...] rt.cpan.org>
Content-Length: 1024
Download (untitled) / with headers
text/plain 1024b
On Mon, Sep 22, 2014 at 06:30:42PM -0400, Chris Hughes via RT wrote: Show quoted text
> Queue: MooseX-Storage > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=99068 > > > Sure - hope this helps:
Thanks, it will be. However, without being able to reproduce this issue, we'll be unable to solve it... so even more helpful would be to nail down what is leaking. Can we be sure it is MooseX::Storage? First, we should look at some common sources of problems. Are you serializing deeply nested objects that might have cycles in them? Test::LeakTrace, Devel::Cycle and Test::Memory::Cycle can identify if this is the case. (http://blog.woobling.org/2009/05/become-hero-plumber.html is my go-to reference for identifying leaks in my code.) Also, finding the things that are leaking would also help -- the tool I like to use for this is Devel::Gladiator: using it to capture the state of the arena after the 2nd and 3rd serialization run can identify what is changing. "I liked it so much, I became its maintainer! (tm)"
MIME-Version: 1.0
X-Spam-Status: No, score=-5.598 tagged_above=-99.9 required=10 tests=[AWL=1.000, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, FROM_OUR_RT=-4, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
In-Reply-To: <rt-4.0.18-10676-1411432499-593.99068-6-0 [...] rt.cpan.org>
X-Spam-Flag: NO
X-RT-Interface: API
References: <RT-Ticket-99068 [...] rt.cpan.org> <CAPPXNB6whAHp73Vt27vY+ELgi6nPVM1a0gn5sswvHH6WywRFpw [...] mail.gmail.com> <rt-4.0.18-4248-1411422573-1742.99068-4-0 [...] rt.cpan.org> <20140922221005.GS79240 [...] tequila> <rt-4.0.18-857-1411423818-257.99068-6-0 [...] rt.cpan.org> <CAPPXNB6F7UZ5Z66mTCeWmcTw0pw9NArGTO37g-RXc8Rh-vx9Qg [...] mail.gmail.com> <rt-4.0.18-32262-1411425041-489.99068-5-0 [...] rt.cpan.org> <20140923003441.GU79240 [...] tequila> <rt-4.0.18-10676-1411432499-593.99068-6-0 [...] rt.cpan.org>
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
X-Received: by 10.50.83.100 with SMTP id p4mr1871685igy.46.1411432863845; Mon, 22 Sep 2014 17:41:03 -0700 (PDT)
Message-ID: <CAPPXNB6fPOEROtWSU3i2zEpAP7DrKevJf=4U0-+D68C9e8dkNw [...] mail.gmail.com>
Content-Type: multipart/alternative; boundary="089e0111c3da7955620503b0d220"
X-Spam-Score: -5.598
Authentication-Results: hipster.bestpractical.com (amavisd-new); dkim=pass header.i= [...] gmail.com
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id 2486D2404E1 for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 20:41:13 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4IvaaRXqs11t for <cpan-bug+MooseX-Storage [...] hipster.bestpractical.com>; Mon, 22 Sep 2014 20:41:11 -0400 (EDT)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id 633D62403A6 for <bug-MooseX-Storage [...] rt.cpan.org>; Mon, 22 Sep 2014 20:41:11 -0400 (EDT)
Received: (qmail 5917 invoked by alias); 23 Sep 2014 00:41:10 -0000
Received: from mail-ie0-f172.google.com (HELO mail-ie0-f172.google.com) (209.85.223.172) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Mon, 22 Sep 2014 17:41:07 -0700
Received: by mail-ie0-f172.google.com with SMTP id rp18so6626279iec.3 for <bug-MooseX-Storage [...] rt.cpan.org>; Mon, 22 Sep 2014 17:41:04 -0700 (PDT)
Received: by 10.107.160.17 with HTTP; Mon, 22 Sep 2014 17:41:03 -0700 (PDT)
Delivered-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
Subject: Re: [rt.cpan.org #99068] Memory Leak with MooseX::Storage
Return-Path: <chris.lokku [...] gmail.com>
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=Y3cqp1pjJfmj+/jlS7l6Mx8xjzZiA2egnPNk1MJW4Ig=; b=ihow+wvXX7RAjSsoeDvjBoB2sX5fi6GkCBa6bTYS3O+abn+XKi7/XfMciWpw4dAauf ehksZhlWnHKI3L0JzTffIc78ZBsZoIV5GdsUyzoPPYCfuJfrFYknf8xC7K7jA+SOKIIJ pV8JeIBa4K4446AJkhJoFyeLT+okR3r9GW9G6QNCf62bvx9QoTV+cfBkWTOiISju5CiZ 1GA15Eg8NodCIpqdFXOb6wr0lN28uxqdEhC+5JBNYxGofdpO6v0Wj33WrcWKSK4CeIde jSf1GSS51Nnr4D65gjBdETDFDuU5rcJ1Q2dhdShwHdZZRGqvKwHmPDesMtTV0oktR10L znTg==
X-Spam-Check-BY: la.mx.develooper.com
X-Original-To: cpan-bug+MooseX-Storage [...] hipster.bestpractical.com
X-RT-Mail-Extension: moosex-storage
X-Google-Sender-Auth: qNhyzKUqZbkz8-cXF4c1nTaZnv8
Sender: chris.lokku [...] gmail.com
Date: Tue, 23 Sep 2014 01:41:03 +0100
X-Spam-Level:
To: bug-MooseX-Storage [...] rt.cpan.org
From: Chris Hughes <chris [...] lokku.com>
RT-Message-ID: <rt-4.0.18-10676-1411432873-899.99068-0-0 [...] rt.cpan.org>
Content-Length: 0
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Content-Length: 1266
Download (untitled) / with headers
text/plain 1.2k
Does my example not reproduce it for you? On 23 September 2014 01:34, Karen Etheridge via RT < bug-MooseX-Storage@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=99068 > > > On Mon, Sep 22, 2014 at 06:30:42PM -0400, Chris Hughes via RT wrote:
> > Queue: MooseX-Storage > > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=99068 > > > > > Sure - hope this helps:
> > Thanks, it will be. However, without being able to reproduce this issue, > we'll be unable to solve it... so even more helpful would be to nail down > what is leaking. Can we be sure it is MooseX::Storage? > > First, we should look at some common sources of problems. Are you > serializing deeply nested objects that might have cycles in them? > Test::LeakTrace, Devel::Cycle and Test::Memory::Cycle can identify if this > is the case. (http://blog.woobling.org/2009/05/become-hero-plumber.html > is > my go-to reference for identifying leaks in my code.) > > Also, finding the things that are leaking would also help -- the tool I > like to use for this is Devel::Gladiator: using it to capture the state > of the arena after the 2nd and 3rd serialization run can identify what is > changing. "I liked it so much, I became its maintainer! (tm)" > > > >
content-type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Content-Length: 1967


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.