Re: PHP has encountered an Access Violation at 00C4DA27

Personally, I would think XP is extremely buggy on the memory allocation part... It seems unable to handle LOTS of allocations/reallocations after eachother... I made a program, which can do one allocation 260 times or so.. Then it crashes... I haven't seen any logic at all in this... for(i=10000;i<100000;i++)free(calloc(i,sizeof(char))); Basicly that crashes it, after a couple of loops... :s Doesn't make any sense to me... Maybe I've missed something though... -- // DvDmanDT MSN: dvdmandt¤hotmail.com Mail: dvdmandt¤telia.com "Amk" <never_slept@yahoo.com> skrev i meddelandet news:20040122183844.43116.qmail@pb1.pair.com... > PHP has encountered an Access Violation at 00C4DA27 > > I'm getting this error a lot with an intensive script I'm running. Though > I've also seen it with other, less intensive scripts in the same project. > > I will get the error 10 times in a row. Then have the script run ok > for a while. This is on Windows XP SP1 with PHP 4.3.4 stock install except > for GD image (v2.0.15) library extensions loaded. Using MySQL for the > database running as a service (v 4.0.17). > > The script it's self is doing a lot of file reads/writes processing several > directories of files 1Mb-10Mb binary (save game files) parsing out various > data including some png images which I'm processing using GD library of > functions making four new images for each file processed and writing those > to disc. Additionally for each folder a MySQL insert is done, and for each > city an insert is done. Typically this is processing around 90 files and > takes 10-20 seconds (when it works). > > I've increased the memory limit to 20mb limit using the php.ini. I've tried > using the > cgi instead of the asapi module - which then just crashes, bringing up the > dr watson 'report this error to MS or not' dialog instead of the access > violation error. > > I've tried commenting out many of the image write functions from the script, > then the mysql calls to see if its the quanity of disk activity or the mysql > calls is contributing to the problem - but it didn't reduce the frequency > and the problem persisited. > > Any help would be appreciated.