For example, if now roll back to that older version of direct call to
database, just using mysqli's sort of direct query, instead of using the
mysqli_statement object, it does seem to try to render image, without
generating direct errors, FWIW - bit slow - and, trying to explain to sort
of site
If I sort of combine all the relevant code - since it's currently a page
instantiating a classe called template, which then calls a function from
another sort of wrapperr class, it's effectively the following - will add
comments in to show where it might be changing context slightly - and, below
OK, seems what's causing issue is imagecreatefromstring(), since, directly
after retrieving longblob data from database, memory usage is:
3402136 = 3.*Mb
and, then immediately after that calling:
$imgOut = imagecreatefromstring($bOut);
and, return that $imgOut variable to calling function, befo
Eric Stenson in php.windows (Thu, 25 Jul 2013 18:35:25 +):
>I've filed bug https://bugs.php.net/bug.php?id=65338 to track this
>issue. The root cause of the AV is when more than one module hooks the
>interned strings, a "wrong" value will be left in
>CG(interned_strings_start), which the Zend
Hello Pierre,
Friday, August 16, 2013, 5:38:01 AM, you wrote:
> and 'TESTUN~1.PHP' has unicode, created using CreateFileW with
> 'testunicode-ßäü123-öâ.php' as path. Fetch the 8.3 path and use it to
> open the file using php, works. In other words. exactly what your COM
> script does. Now, why y
Production server says following about version:
PHP Version 5.3.3-7+squeeze16
My local machine is running on XAMPP, with PHP 5.3.5.
Let me try out the memory_get_usage() [1] as well to see if can find out how
much memory is being used up, when, and by what part of process.
FWIW, here are the
