-
Notifications
You must be signed in to change notification settings - Fork 35
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
chapter_08 #23
Comments
Thanks for the bug report. Unfortunately, I can't reproduce the problem. What platform are you on? If you're on Linux, which distribution (and version thereof) are you using? Which version of perl are you using (the output of As far as the chapter text is concerned, if I recall correctly, @xsawyerx made the comment at a conference recently that he's thinking of reworking this chapter, and I have a feeling that it's a known issue that the chapter isn't yet complete. |
Hi Paul, it is Linux 64bit and perlbrew and it fails on each Perl dist (each 64bit) so far, which was 5.14.0 w/ threads, 5.14.1 w/o threads, 5.16.2 w/o threads and 5.22.0 w/o threads. I found the setting 100/100 for Test::MemoryGrowth suspicious, and indeed it worked for that number, but not when I run with a more reasonable setting like the default 10/10000. Did you also run you test with Test::MemoryGrowth default? |
No, I simply ran the test suite. However, after I changed the number of calls to 10000 and the burn in setting to 10 (or even 100), I'm able to reproduce your results. Thanks for pointing out this issue we'll need to look into it a bit more. @xsawyerx: was there a reason you chose |
Afaik Perl reserves system memory in bigger chunks. With just 100 calls the leaked memory seems to stay below the threshold before Perl must reserve the next chunk. |
No reason it was exactly 100. I just wanted something that didn't take very long. Let's raise and try to fix any problem we see. |
I tested with 1,000 for both
I'm going to review the chapter now and clean up the code first. Then we'll see if the code still leaks and try to address that. Thanks again for opening the ticket. :) |
This doesn't seem to happen every time I run the test. I'm not sure why it's sporadic. |
First of all: Many thanks for this great tutorial.
Unfortunately the last chapter is not complete. Moreover the example code is broken.
The text was updated successfully, but these errors were encountered: