Closed (fixed)
Project:
SWF Tools
Version:
6.x-2.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Mar 2009 at 15:55 UTC
Updated:
1 Apr 2009 at 13:35 UTC
AFter updating to 2.4 and running update.php, it bombs here.
Fatal error: Out of memory (allocated 33030144) (tried to allocate 659512 bytes) xxx/includes/database.mysql.inc
Comments
Comment #1
Stuart Greenfield commentedI'm not sure that's an SWF Tools issue. The new package recommends to run update.php to ensure that the new themes get registered since running the update causes the theme registry to be rebuilt. However, SWF Tools itself doesn't actually try to run any update code of its own since it has no database tables associated with it. It sounds like something is else is maybe trying to run a large update and causing the memory limit to be exceeded. If you try to rerun update.php you could check on the list of available updates to see what modules are trying to run updates, and then see if there are any known issues with their upgrades?
The other way to initialize the new SWF Tools themes is to go the modules page simply hit save without changing anything. That should cause the theme registry to rebuild so you can get the new version of the module working.
I'm not sure what status to assign to this as I'm not sure there is anything to be done from an SWF Tools perspective?!
Comment #2
dan.crouthamel commentedI'm not sure either :) If I disable the module, I can run update.php just fine. If I enable it, update.php fails. I'll play around with it some more and see if I can narrow down the problem.
Comment #3
Stuart Greenfield commentedThat sounds very odd - I'm not sure why that should be. If you have disabled and re-enabled SWF Tools then the new themes will at least be registered!
I've not experienced this issue locally. Are you running a lot of contributed modules? Can you run update.php if you leave SWF Tools enabled but disable something else, just in case it is the "volume" of modules?
I'll leave this thread open for now in case anyone else experiences this issue.
Comment #4
dan.crouthamel commentedI think you're right. I'm beginning to suspect that the Panels module is really the problem here, but I could mistaken :) I'll close this as I don't think SWF Tools is the issue anymore - sorry for the false alarm :)