Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Email-Address CPAN distribution.

Report information
The Basics
Id: 19163
Status: resolved
Worked: 5 min
Priority: 0/
Queue: Email-Address

People
Owner: rjbs [...] cpan.org
Requestors: adamk [...] cpan.org
Cc:
AdminCc:

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



Subject: Allow the cache to be permently disabled
The parse cache acts, in effect, as a memory leak. In situations where you are trying to minimise memory usage, and/or process a _lot_ of email addresses, continuous manual action is required to "free" this memory. At one extreme, this means that you need to purge the case after every parse call, in order to keep it empty. For these situations, some of $Email::Address::NOCACHE flag should be able to be set. This would not prevent existing cache values from being used, but would prevent new parsed addresses from being added.
Subject: Re: [rt.cpan.org #19163] Allow the cache to be permently disabled
Date: Tue, 9 May 2006 09:25:52 -0700
To: bug-Email-Address [...] rt.cpan.org
From: Casey West <casey [...] geeknest.com>
On May 9, 2006, at 7:45 AM, Guest via RT wrote: Show quoted text
> The parse cache acts, in effect, as a memory leak. >
Nice spin. :-) Show quoted text
> In situations where you are trying to minimise memory usage, and/or > process a _lot_ of email addresses, continuous manual action is > required > to "free" this memory. > > At one extreme, this means that you need to purge the case after every > parse call, in order to keep it empty. > > For these situations, some of $Email::Address::NOCACHE flag should be > able to be set. >
I like it. This is a good plan. -- Casey West
Subject: Re: [rt.cpan.org #19163] Allow the cache to be permently disabled
Date: Wed, 10 May 2006 08:09:45 +1000
To: bug-Email-Address [...] rt.cpan.org
From: Adam Kennedy <adam [...] phase-n.com>
Casey West via RT wrote: Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=19163 > > > > On May 9, 2006, at 7:45 AM, Guest via RT wrote:
>> The parse cache acts, in effect, as a memory leak. >>
> > Nice spin. :-)
It's _always_ about perspective :)
I have added enable_cache and disable_cache methods in the Subversion repository. The cache is still enabled by default.
Released. -- rjbs