Last modified: 2013-03-19 22:44:00 UTC
I'm not sure if bug reports still get read these days, but here goes anyway. Since the upgrade to SMW 1.8.0.4, I frequently get the following error message: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 8208 bytes) in ..../extensions/SemanticMediaWiki/includes/storage/SQLStore/SMW_Sql3SmwIds.php on line 835 The line in question appears to be "return unserialize( $hash );" More sporadically, one of these messages appears: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32 bytes) in ...includes/GlobalFunctions.php on line 874 Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 326 bytes) in ...includes/GlobalFunctions.php on line 859 Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 64 bytes) in ...includes/db/Database.php on line 1948 I've already set $wgMemoryLimit to "1024MB", so this may not represent an actual memory issue. FWIW: * I noticed that the table "smw_object_ids" is nearly as large as "text". * While previously a data refresh could be run overnight, it now took five or six days to complete. * See my other bug reports for possibly related issues * No shell access available Specifications: MW 1.19.2 PHP 5.3.3-7+squeeze15 (cgi-fcgi) MySQL5.1.66-0+squeeze1
What do you mean as large as *text* ? Anyways, I think this is less a bug and more of a resource scarcity issue. Your best bet would be to increase the memory size
The largest table is called "text", followed hot on the heels by "smw_object_ids". There should be sufficient harddrive space, but I suppose you're referring to RAM? I've just set $wgMemoryLimit to "2048MB", but isn't thata bit unusual?
