On Fri, April 13, 2007 12:54 am, Arthur Erdös wrote: >>> It can if you're trying to process a borked image... >>> >>> I've had imagecreatefromjpeg() eat memory up to almost 50x the size >>> of >>> the image before finally deciding it can't handle it and crapping >>> out. >>> That was *after* running it through getimagesize() with no problem >>> at all. >> >> okay - good point - but in this case the OP is reading in an html >> template file, >> just a string of 20.7Kb, what could go wrong there? >> > > this is probably one issue... the template is an HTML template > containing images like <img src="http://www.brainguide.com/xxx"/>. How > does PHP handle this stuff? I suppose that it is just a string and the > image at the URL is not really read, or am I wrong? > > The newsletter does not have any attachements. Now you're not making any sense at all... Either your newsletter has the images in it, or it doesn't. I suspect that it's set up to take that newsletter *AND* all the images, and bundle that up into a nice *BIG* HTML Enhanced (cough, cough) email, and send that out... If you don't free up that template, that could be a large chunk of RAM right there. -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
