Ron Savage ([EMAIL PROTECTED]) wrote on 11/23/2007 05:39:05 PM:
> > The problem seems to be that imagemagick won't let go of the file.
> 1) Under Unix-like OSes it's possible - roughly speaking - to open a
> file and, while holding it open, delete it from the directory, so the
> process which has it open is the only process which knows about the
> file.
[..]
> 2) Have you considered forcing this part of your code into a new scope,
> just by adding a pair of {}, so exiting the scope causes Perl and hence
> IM to release resources. Just a not-so-wild guess.
I'm actually getting intruiged in figuring out what it really is doing.
Here is the code from the calling routine:
print "Entering buildTab with PID $processID tab index $index\n" if
$opts{'d'};
my $tempPNG = &buildGraphic($processID, $project);
print "DEBUG2: back from routine, is it still open?";
my $pause = <>;
At this point, the calls to image::Magick are a dim history inside the
buildGraphic routine, so IM shouldn't be in play.
Its possible that File::Temp still has it open, I don't know, but process
explorer still shows an open handle to the file.
I'll recode File::Temp out of it and see if its still there.
--woody
--
Dr. Robert "Woody" Weaver Security, Privacy, Wireless, and IT
Governance
IT Security Architect Phone: 240-782-4260
--
Stop! Whoever crosseth the bridge of Death, must answer first
these questions three, ere the other side he see!
"What is your name?"
"Sir Brian of Bell."
"What is your quest?"
"I seek the Holy Grail."
"What are four lowercase letters that are not legal flag arguments to the
Berkeley UNIX version of `ls'?"
"I, er.... AIIIEEEEEE!"
_______________________________________________
Magick-users mailing list
[email protected]
http://studio.imagemagick.org/mailman/listinfo/magick-users
