• I’ve been using this plugin on a client’s site for a while without thinking much of it, but after investigating a complaint of a sluggish UI, it turns out this plugin is responsible for a 500 MB memory increase when only two SVG files are displayed on the page.

    Enabling SVG support for the WordPress media library can be done with a dozen lines of PHP, so just switching form this plugin to a few lines in functions.php has returned RAM consumption back to normal again.

    I previously wrote that this plugin appears to convert SVG to HTML and CSS, but that’s not actually the case—that turned out to be the Safari LiveText implementation. The plugin does nevertheless trigger a memory leak. I haven’t investigated it further, but the developer is welcome to comment on it. I’ll update my review if necessary.

    • This topic was modified 7 months, 1 week ago by elaborate.

The topic ‘Causes significant memory spike’ is closed to new replies.