You goofed and forgot to binmode IMAGE or die "Couldn't binmode image". Always do that when working with binary data. You also never close FH. If you meant to just return the contents of the file then you're better off writing that as a plain read - you're forcing perl to jump through hoops.

# Ok, could be better local $/; open ( FH , '/path/to/some/image' ) or confess $!; binmode FH or confess $!; my $image = readline *FH; close FH or confess $!; return $image; # Better open ( FH , '/path/to/some/image' ) or confess $!; binmode FH or confess $!; my $image; read FH, $image, -s FH; close FH or confess $!; return $image; # Best open ( FH , '/path/to/some/image' ) or confess $!; my $image; read FH, $image, -s FH; close FH or confess $!; return \ $image;

In reply to Re: CGI::Application + mod_perl =|!= memory leak by diotalevi
in thread CGI::Application + mod_perl =|!= memory leak by submersible_toaster

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.