#42062 [Asn]: imagegrabscreen() returns corrupted GD resource

ID: 42062 User updated by: fumble1 at web dot de Reported By: fumble1 at web dot de Status: Assigned Bug Type: GD related Operating System: Windows XP (Home Edition) PHP Version: 5.2.3 Assigned To: pajoye New Comment: Guess I was on the wrong track... that "file-can’t-be-deleted-'cause-it’s-used-by-another-process" thingy is caused by the imageoutput-functions failing on memory_limit. Sorry for accusing imagegrabscreen(). pajoye> "Increase your memory limit." That got me an all-black PNG the size of my screen, just to note that. Previous Comments: ------------------------------------------------------------------------ [2007-07-21 19:25:09] pajoye@php.net Thanks to Derick, I miss the "can't be deleted" part. ------------------------------------------------------------------------ [2007-07-21 19:06:30] pajoye@php.net "Fatal error: Allowed memory size of 8388608 bytes exhausted" Increase your memory limit. ------------------------------------------------------------------------ [2007-07-21 19:01:45] fumble1 at web dot de Description: ------------ imagegrabscreen() returns a corrupted GD resource, which causes imagepng() to bail out. Reproduce code: --------------- <?php $im = imagegrabscreen(); imagepng($im, 'screenshot.png'); ?> Expected result: ---------------- A screenshot being created in the working dir or an error message from imagegrabscreen(). Actual result: -------------- "Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 3840 bytes) in __FILE__ on line 3" (imagepng()) and an empty PNG-file that httpd.exe kept open, so it couldn’t be deleted. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=42062&edit=1