svn[1337] Error on guild update

by **boyo** » Wed Sep 19, 2007 11:40 am

I recieved the following error, after a very fresh install of roster.
(btw, 'DROP DATABASE `sovereign`' in mysql was not the right button to click on.)

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 24576 bytes) in C:\wamp\www\roster20\cache\tpl_default_footer.html.inc on line 17

No debug or sql data was shown.

I have the update log, but it shows nothing special. Just looks like a normal update.

by **boyo** » Wed Sep 19, 2007 11:53 am

Ok, I'm not sure how I did it or hwat happened, but... I tried to reproduce the error, and couldnt get it to do it.

I'll keep tinkering and see if i can find how to reproduce it.

Edit:
Ok, I figured out how to reproduce it.
Install a fresh copy of roster.
Set upload rules
Install memberlist addon
Install SMFSync[14]
Upload guild data.
Recieve error.

I thought it was maybe just SMFSync causing it, so i installed only that, and it didnt do it. Installed only memberlist , and it didnt do it. It's the combination of the 2.

by **zanix** » Wed Sep 19, 2007 12:25 pm

php is running out of it's allocated memory

We have trimmed update.lib.php to be as nimble as possible and even it can cause this error

by **PleegWat** » Wed Sep 19, 2007 12:35 pm

Check the title: This is indeed an update issue.

There have been improvements to lighten the load in roster 2.0, but the structural problem is deeper. Even if this were completely fixed in the core roster, then addons can easily use a lot of memory (like you are seeing the problem only appear if you install two addons that have update triggers, and probably cache stuff).

The problem is inherit in the way the update process is set up, and the update process would have to be completely rebuilt from scratch with memory usage in mind, to fix this. Which is not going to happen on the 1x codebase.