Title: Fatal error Last modified: August 30, 2016 --- # Fatal error * Resolved [redhawkssupport](https://wordpress.org/support/users/redhawkssupport/) * (@redhawkssupport) * [11 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-1728/) * I have been using your plugin since the begining, always loved it and not alot of trouble. After the update i get error all over the place. * Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 34298801 bytes) in /storage/content/85/HIDDEN-BY-ME/icehockey.se/public_html/ wp-includes/wp-db.php on line 1092 * I’m using latest version of DIVI THEME and WordPress and i have diabled all other plugins, to be honest, i’ve tried all i can to fix it myself before asking you here. * Site using the plugin is [http://www.icehockey.se](http://www.icehockey.se) . the plugin is for now not activetaed, in fact i ubinstlled it since it was eating memory and almost made tnhe site stopp working completly. Please get back to me if you need more info. * // Benny * [https://wordpress.org/plugins/ad-blocking-detector/](https://wordpress.org/plugins/ad-blocking-detector/) Viewing 9 replies - 1 through 9 (of 9 total) * [John Morris](https://wordpress.org/support/users/jtmorris/) * (@jtmorris) * [11 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-1728/#post-6354499) * Hello, * I’m sorry the update caused problems. * I have released a new version of the plugin (version 3.0.2) which makes some performance improvements and reduces memory usage. * Can you please try installing the newest version of this plugin and seeing if the problem persists. Make sure that you have or create one or more shortcodes as the database interactions regarding shortcodes are what use up memory for this plugin. * —– * **If the problem goes away**, can you copy and paste the contents of the “Plugin, WordPress, and Server Configuration Data” box and the “Session Log” box on the“ Report a Problem/Debug” tab. Pasting it in an email is fine, if you’d rather not share that information publicly. * I haven’t had any memory related problems on the 9 websites I have Ad Blocking Detector installed on, and some of those I forced the available memory to a very small amount to test. It never appears to exceed 1 MB of memory usage. The information requested above will hopefully give me some insight as to why Ad Blocking Detector is such a memory hog on your site. * —– * **If the problem does not go away**, can you send me the memory usage of your site with Ad Blocking Detector disabled or uninstalled. An easy way to get memory usage is with the [WP-Memory-Usage](https://wordpress.org/plugins/wp-memory-usage/) plugin. It will add a box to your WordPress dashboard called “Memory Overview.” A screenshot or the copied and pasted text is fine. * Examples: Copy & Paste: * ``` PHP Version : 5.4.41 / 32Bit OS Memory limit : 40 MB Memory usage : 14.34 MB ``` * Screenshot: [http://1drv.ms/1g77YnP](http://1drv.ms/1g77YnP) * Thread Starter [redhawkssupport](https://wordpress.org/support/users/redhawkssupport/) * (@redhawkssupport) * [11 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-1728/#post-6354513) * This is not going so good i’m afraid. I did reinstall and for a moment all was ok. First the plugin told me i have no shortcodes. After creating a new shortcode and save the old shortcodes was back. Then, trying ti delete the old code and save all i got was a white page. * Secondly, going to the site to “have a look” gives a result where only part of the site is shown. Only way for me to avoid whitepage was to use ftp and then rename plugin by hand to disable it. * Should i go into php-admin to remove all about the plugin and then reinstall from schratch? * // B * [John Morris](https://wordpress.org/support/users/jtmorris/) * (@jtmorris) * [11 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-1728/#post-6354586) * If you have access to a tool like phpMyAdmin, where you can manipulate the database, then yes, this would be helpful. Normally, uninstalling the plugin from within WordPress would delete _almost_ everything, but since it’s crippling your site, it probably won’t work correctly and will need doing by hand. * From the wp_options table, everything with “abd_” and “_transient_abd_” in the option name column can be deleted. If you want a list of items, you can run this SQL query on the database: * ``` SELECT * FROM wp_options WHERE 'option_name' LIKE '%abd_%' ``` * The exact result will vary depending on your site. Here is a screenshot of the output from one of my testing sites, for comparison’s sake: [http://1drv.ms/1MKLfb9](http://1drv.ms/1MKLfb9) * Once the wp_options table is emptied, you’ll need to stop Ad Blocking Detector from trying to migrate your old shortcodes. In versions 1 and 2 of this plugin, shortcodes were stored in the wp_abd_shortcodes table. The plugin tries to migrate the shortcodes in that table to the new storage method, and this may be the problem. * If you don’t mind losing the shortcodes, then you can delete/drop that table. If you don’t want to lose them, then you can rename/move the table, or export the table’s contents for later import and then delete/drop the table. * Then, finally, delete the plugin folder with FTP. * Normally, almost all of that is done by “uninstalling” the plugin from the WordPress dashboard. This is probably not reliable since the plugin is failing. The only important step not done is deleting the wp_abd_shortcodes table, as I’m waiting to fix any unexpected problems with the update process before removing the old shortcodes. * —– * Once all this is cleaned up, then install the plugin from scratch from the WordPress. org repository. * If the reinstall seems to work, then try sending the “Session Log” and “Plugin, WordPress, and Server Configuration Data” boxes before creating any shortcodes as it seems that’s when it starts to fail. * Then, try creating a shortcode or two and seeing how it behaves. * If you need help with any of the above steps, let me know and I can go into more detail. * —– * Again, sorry the plugin is misbehaving! * [John Morris](https://wordpress.org/support/users/jtmorris/) * (@jtmorris) * [11 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-1728/#post-6354640) * I am currently aware of 4 people experiencing a similar problem, though it manifests itself different for them. For informational purposes for others reading this, if Ad Blocking Detector dramatically slows down your WordPress admin, you see PHP errors regarding memory, or the page seems to stop loading in the middle, this applies to you. * —– * I was able to replicate this problem by creating ~50 shortcodes, and lowering the available memory for WordPress substantially below normal. Using that as a test platform, I have made some dramatic performance improvements, and built in some performance measurements and collection. * —– * If you’re willing to give Ad Blocking Detector another try, then **version 3.1.2 has these latest improvements**. If the problem persists, let me know. As before, if you can access the “Report a Problem / Debug” tab, and give me the output in the textboxes under “Session Log” and “Plugin, WordPress, and Server Configuration Data”, that will help. * If the problem has seemingly been fixed, then, if you can click the “Clear Log” button under “Session Log,” refresh the page a few times, then send me the results in the “Session Log” textbox, it should contain some helpful performance data. I can then verify whether the problem is fixed, or simply reduced. * —– * If anyone reading is familiar with PHP programming and curious why this was occurring, it was because of PHP’s ineffective garbage collection when using circular references in classes and objects ([http://paul-m-jones.com/archives/262](http://paul-m-jones.com/archives/262)). Using circular references results in a sort of memory leak. This problem is exacerbated in older versions of PHP. * These circular references were only created on the WordPress dashboard, or when logged in as an administrator. Due to limitations in the WordPress Settings API( registering settings must be triggered by the admin_init hook), these references were created on every page load in the WordPress admin section, rather than solely on Ad Blocking Detector’s pages. This is why, for the few experiencing problems, it seemed to cripple the whole website, and the plugin could not be removed without deleting or renaming the plugin directory. * The version 3.1 branch of this plugin eliminates all circular references, reduces the amount of data stored in the WordPress database, and monitors and logs plugin performance. This resulted in about a 90% reduction in used memory on my sites, and, should presumably be far more effective on sites experiencing a higher magnitude of memory problems, since the memory leak was evidently far worse for them. * Thread Starter [redhawkssupport](https://wordpress.org/support/users/redhawkssupport/) * (@redhawkssupport) * [11 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-1728/#post-6354641) * Hi! VERY early morning here in Sweden – i couldn’t go to bed before trying and testing 🙂 I won’t give up on you or your plugin and am doing my best overhere to try to find out why, how and when. * I’m “fu>