ID: 11829
User updated by: [EMAIL PROTECTED]
Status: Closed
Bug Type: IIS related
Operating System: win2000professional
PHP Version: 4.0.4pl1
New Comment:

Failure to release memory is the first thing we look at when this error occurs.  So 
there are two ways to look at this problem.  First, the php function may cause memory 
leaking.  Second, C program does not do a decent job on releasing the resource.  Since 
my program consistently uses C to recall the function fsockopen() from php to open 
websites.  I decided to abandon the function fsockopen() in php and decided to adopt C 
in order to fix the problem. However the problem persistently occurred, so I 
the C program and found out that during the creation process the program fails to 
complete the close handle progress.  After fixing the problem, I did a few more tests 
and found out that the Memory Access violation problem no longer exists.

Previous Comments:

[2001-07-23 14:31:01] [EMAIL PROTECTED]

Looks like a Mem Access violation, probably from some thread safe issue, this also 
doesnt seem IIS related as you mention the console, Please remove all extensions from 
your php.ini and see if the memory access violations continue if they stop then add 
the extensions gradually and tell us which one causes the mem access violation to 
occur as it probably isnt thread safe although this shouldnt effect the console. 
Anyway there isnt enough information here if you can reproduce it reliably please 
reopen this bug report including how you reproduce it with a short script.

- James


[2001-07-02 02:59:41] [EMAIL PROTECTED]

Is it possible that you can shorten down your script to the point where the problem 
still occurs, or provide the script in this bug report?



[2001-07-02 02:31:01] [EMAIL PROTECTED]

I've writed a scheduling program with C to execute php application all day in the 
console mode.Sometimes will happen the following error message:
   The instruction at "0x78003abf" referenced memory at "0x0111a000".The memory could 
not be "read".

This situation would not crash my C program.I only have to do is close the error 
message.But it will happen again after 3 or 4 hours.
Do you have any idea about this situation?



Edit this bug report at

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to