Thread

Help,

On clicking the Edit Categories I am getting this error on our development machine:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 233472 bytes) in /vdev/www/htdocs/wsg/blogs/smcBlog/cp/cp.publish.php on line 9248

Why?

Also, on our staging and production machines, a related issue is that the same Edit Categories link is generating a blank page for those who should be able to do so.

All machines are PHP, MySQL, Apache and SUSE Linux most current.

All machines were recently upgraded form EE 1.4.2 to EE 1.6 following the prescribed upgrade procedure.

Any assistance would be appreciated.

Thanks

John

I’ve moved this to our technical support forums for you.  Have you seen this kb entry?  I suspect the blank page is just a similar error, just suppressed, so we should give this a shot first and see if your host will up you to 16 or 32meg memory.

Yep, we are at 8M now, going to get that reset to 16M now.

In general, just today, for what ever reason I having difficulties with this. It seemed to be working previous ly, version 1.4.2,  but frankly I am not sure if it was working after the upgrade.

Can you give me any reasons not to increase it to 32M? My instincts tell me to do that just to be safe however I am not a PHP tech so I can only guess what the overall impact on the server would be.

Any thoughts?

1.6 introduced some major category changes so it may just be that coming into play.  You can certainly increase it to 32m, the more the merrier.

I am going to follow my instincts and go with 32M.

I know you guys are on top of your game but FYI:

“
Memory Management >> In C, you always have to worry about memory management. This still holds true when writing PHP extensions in C, but the extension API provides you with a safety net and some helpful debugging facilities if you use the API’s memory-management wrapper functions (you are strongly encouraged to do so). The wrapper functions are:

  emalloc( )
  efree( )
  estrdup( )
  estrndup( )
  ecalloc( )
  erealloc( )
“

I am hoping that you all are implementing some kind of memory safety method(s).

In any case I will let you know how it goes.

Thanks

John