New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verilog-Perl memory leak? #232
Comments
Original Redmine Comment Well the post butchered my code example. Let me know if you want me to provide an actual .pl Jeff |
Original Redmine Comment Are you using the most recent release? I thought all leaks were fixed in 2.230 - you'll see the t/48_leak.t test has almost the exact same loop you describe. So, maybe it's data dependent. |
Original Redmine Comment Wilson Snyder wrote:
Thanks for pointing me at that. So the difference between your test and mine is: If you have this then there isn't any memory growth. Without it the memory continues to grow. Jeff |
Original Redmine Comment Resolved... delete is needed. Based on your problems I looked at using weak references to solve this problem, but it can cause |
Author Name: Jeff Short
Original Redmine Issue: 232 from https://www.veripool.org
Original Date: 2010-04-05
Original Assignee: Wilson Snyder (@wsnyder)
I don't know if this is a Verilog-Perl problem or a problem with perl.
If you do the following:
foreach my $vfile () {
my $nl = new Verilog::Netlist(....)
$nl->read_file(filename=>$vfile);
undef($nl);
}
You will see the memory grow with time, even if all the verilog files are the same size. It seems to me that the memory usage should be the that to cover the largest $nl ever used.
Jeff
The text was updated successfully, but these errors were encountered: