Most of Sapling's processing is done on a backend server, remote from the computer where the browser extension or application plugin is installed. This means that the memory (RAM) and compute (CPU) footprint of Sapling should be small.
However, sometimes you may observe lag or freezing after installing a new extension. How can you determine if Sapling is the cause? This article describes some ways to diagnose the issue as well as how to report any issues to the Sapling development team.
Chrome Extension Lag
If you're experiencing delays with the Chrome extension, first try the following:
Under the Window menu, click Task Manager.
You should arrive at a window that looks similar to this:
Look for Extension: Sapling... and check the CPU and memory footprint. Compare it to the CPU and memory usage of the other extensions and tabs.
If usage is high, try disabling Sapling to see if the issue goes away. Then enable Sapling again to see if the issue pops up again.
If you think lag or freezing is due to Sapling, please email firstname.lastname@example.org with the following:
- The extension/add-on you were using.
- The hostname of the website where the issue occurred (e.g., https://google.com), if applicable.
- Any screenshots (e.g., of Task Manager or the webpage where the lag occurred) that you're able to share.
The purpose of sharing this information is so that the Sapling team can reproduce the issue and fix it in our next product update.