[15:27:42] E [23:34:27] I am having an issue since upgrading to MW 1.43 that my wiki family's favicon is only set on the subdomain root. Going to any page reverts to the favicon present in the mediawiki install root dir. [23:35:29] My setup is that all of the wikis are installed on the same server, using a shared MW installation. I set the favicon to $wgFavicon = "assets/$wikiID/favicon.ico"; and each wiki is present on a subdomain of the main domain. [23:37:36] And some pages seem to never grab the favicon at all [23:45:40] Ah I fixed it, had to use "$wgScriptPath/assets/...". Oops. [23:46:04] Running into a different issue with the GlobalBlocking extension, where it seems to be causing a memory leak when enabled. [23:46:21] that sounds like fun [23:46:25] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/mediawiki/includes/Permissions/PermissionManager.php on line 1557 [23:46:43] What's the stack trace look like? [23:46:50] How do I enable the stack trace? [23:46:56] If it's semi-replicable, it probably wants dumping in phab [23:46:58] !debug [23:46:58] For information on debugging (including viewing errors), see https://mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging Also see https://mediawiki.org/wiki/Manual:Errors_and_symptoms [23:50:59] Not getting a stack trace with all of those debug settings turned on [23:51:13] error_reporting( E_ALL); [23:51:14] ini_set( 'display_errors', 1); [23:51:14] $wgShowExceptionDetails = true; [23:51:15] $wgDebugToolbar = true; [23:51:15] $wgShowDebug = true; [23:51:16] $wgDevelopmentWarnings = true; [23:52:52] xdebug might be the "best" way, but not something to leave on for production... [23:53:42] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 16384 bytes) in /var/www/html/mediawiki/includes/libs/rdbms/database/DatabaseMySQL.php on line 670 [23:53:45] Oh fun, a new error. [23:54:18] Weirdly, the wiki mostly loads in a new private tab, but not otherwise. Not sure why. I am force-refreshing. [23:55:04] Oh because I am signed in on a non-private tab, that's probably why [23:56:42] There may also be some amount of "268M isn't enough memory to run your wiki as is" [23:58:18] It had been 128MB, does GlobalBlocking really require that much memory? [23:58:27] I doubled it to 256MB [23:59:33] What is the recommended amount? Everything I saw online said 128MB which is why I was using that initially. [23:59:43] Is it just globalblocking causing the problem? [23:59:48] What version did you upgrade from? [23:59:55] Yes, if I disable GlobalBlocking then there are no issues.