Bug #42480 for Win32-Exe: Memory Leak, it seems

Sat Jan 17 06:58:43 2009 cpan [...] dusty.hey.nu - Ticket created

Subject:

Memory Leak, it seems

As noted in: http://www.perlmonks.org/?node_id=736789 Everytime I use: "my $exe = Win32::Exe->new($filename)" tons and tons of memory is used and not released. Each time it's run, it increases the number of references and the process memory goes way up. It seems the larger the file being read, the more memory is being used. I haven't tested, but I assume that the amount of memory used is the same as the size of the file being read. When we leave the scope that it's used in, it still doesn't release.

Tue May 04 04:48:27 2010 mdootson [...] cpan.org - Correspondence added

Hi, Thanks for reporting this issue and providing link to thread with a working solution. There is, as yet, no fix for the memory issues in Win32::Exe. As you have noted, Win32::File::VersionInfo is a better fit for gathering version information from several binaries. As Win32::Exe is mainly targeted at updating single executable or dll files, the memory issue is not a 'show stopper' for the majority of users. I will leave the ticket status 'open'. Regards Mark On Sat Jan 17 06:58:43 2009, WILSOND wrote: Show quoted text

> As noted in: http://www.perlmonks.org/?node_id=736789 > > Everytime I use: "my $exe = Win32::Exe->new($filename)" tons and tons

of Show quoted text

> memory is used and not released. Each time it's run, it increases the > number of references and the process memory goes way up. It seems the > larger the file being read, the more memory is being used. I haven't > tested, but I assume that the amount of memory used is the same as the > size of the file being read. > > When we leave the scope that it's used in, it still doesn't release.

Tue May 04 04:48:27 2010 The RT System itself - Status changed from 'new' to 'open'