php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #42600 Invalid access to memory location.
Submitted: 2007-09-09 03:01 UTC Modified: 2009-12-08 01:00 UTC
Votes:14
Avg. Score:4.4 ± 0.9
Reproduced:13 of 13 (100.0%)
Same Version:8 (61.5%)
Same OS:8 (61.5%)
From: php at littlekp dot ddo dot jp Assigned:
Status: No Feedback Package: EXIF related
PHP Version: 5.2.* OS: Windows
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2007-09-09 03:01 UTC] php at littlekp dot ddo dot jp
Description:
------------
PHP Error appears after restarted the IIS under Windows. The problem of "Invalid access to memory location." is reported when using the php ext although only running phpinfo().

Reproduce code:
---------------
(The bug is produced by running most of the scripts.)

Expected result:
----------------
No Error is expected.

Actual result:
--------------
Actually when I turn off the exif extension, the IIS and PHP are turned back to normal. No more "Invalid access to memory location." occurred. Please check out the php_exif.dll for any bugs.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2007-09-09 06:01 UTC] php at littlekp dot ddo dot jp
ISAPI is being used with IIS 6.0 in Windows Server 2003 STD
Slow computer P3-733 is used with 512MB PC133 RAM
Only phpinfo() is running.
Page is viewed in any computer with IE 6.

Until now, this only happened when turning php_exif.dll on in PHP EXT.
Thanks!!
 [2007-09-09 10:08 UTC] jani@php.net
Does this happen if you don't use ISAPI but use the FastCGI instead (which is the preferred SAPI to use with IIS anyway..) ?
 [2007-09-09 11:09 UTC] php at littlekp dot ddo dot jp
I havent tried as I preferred to use ISAPI rather than CGI (php.exe).
CGI seems unsafe in IIS and hard to configurate.
 [2007-09-10 09:44 UTC] jani@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.


 [2007-09-18 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 [2007-12-19 15:27 UTC] stijn dot peeters at gmail dot com
same problem here.
when activated the exif extension 
php gives an error: Invalid access to memory location. 

when the session.save path is qouted  to disable it, php works once again.
 [2008-01-25 20:55 UTC] mmorrey at digiblue dot com
Same thing here on a fresh install of PHP 5.2.5 on IIS 6 (Windows Server 2003) in ISAPI mode. No messages sent to log file or NT Eventlog. Disabling EXIF cleared error.
 [2008-04-03 02:46 UTC] rwuhrman at yahoo dot com
I just had this problem (exact same error) after installing EXIF also (IIS6, PHP 5.2.4).  Restarting iis did nothing.  However, a reboot thankfully made it go away, before I had to download all the tools to do the backtrace.
 [2009-11-30 11:49 UTC] hasnat at donotrevealfkn1337 dot ccc
encountred same problem winodws 2003 php 5.2.11 ISAPI IIS 6

resolved by checking permissions on these directories

upload_tmp_dir="C:\Temp"
session.save_path="C:\Temp"
error_log="C:\temp\php-errors.log"
 [2009-11-30 11:53 UTC] pajoye@php.net
Try using the FastCGI SAPI. The ISAPI is not supported anymore (by php.net or MS).
 [2009-12-08 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Tue May 11 21:01:26 2021 UTC