I don't have permission to delete reviews, only Mozilla does. I flagged your prior review for inappropriate language and Mozilla decided to take it down. I will flag this one to Mozilla for the same reason—hyperbole and insults are not welcome here.

Constructive criticism is always welcome, even if it's accompanied by a 1-star rating. You can find plenty of examples of how to write constructive criticism in other negative reviews of Tab Stash. (Though I do wish people would reach out using the other ways of contacting me to try to resolve their problem first—I do actually read and respond to bug reports!) A lot of the improvements that have gone into Tab Stash over the years happened only because of the feedback I've gotten from users both here in reviews and on GitHub.

In fact, there is a 2-star review complaining about the exact same issue you faced, but written in a way that was respectful—perhaps you can use that as an example.

Hello, at the moment, there are two known issues (one in Tab Stash and one in Firefox) that can lead to high CPU usage and which I'm looking into for the next Tab Stash release. Fortunately, there are workarounds for both.

First, if you upgraded to Tab Stash 2.10 from an earlier release and you notice high CPU usage after the upgrade, please try uninstalling/reinstalling Tab Stash (simply disabling it isn't sufficient). Pre-2.10 versions had a bug which left some stale deleted-items entries around, and when you first upgrade to 2.10, those entries will be cleared all at once, resulting in the high CPU. Uninstalling/reinstalling Tab Stash is another, faster way to clear out the old entries.

Second, there is a bug in Firefox's saved session handling which can cause Tab Stash to have high CPU usage. Tab Stash tries to work around this bug, but the workaround is what causes the high CPU. The bug seems to have gotten worse in recent Firefox releases and so I'm looking at ways to improve the workaround. In the meantime, however, clearing out any invalid saved-session data usually resolves the problem; you can find instructions here:

https://github.com/josh-berry/tab-stash/wiki/Restart-Firefox-Without-Saved-Session-Data

If neither of these things helps, please feel free to open an issue on GitHub and I'd be happy to troubleshoot further with you there.

Sorry to hear you were having trouble. There's not much for me to go on here, but what you're describing sounds like an issue with Firefox itself that affects a small handful of Tab Stash users, where Firefox's extension APIs sometimes don't work.

This can happen due to Firefox's saved session data getting corrupted. Tab Stash naturally uses Firefox's tab/session APIs quite a bit, so when things don't work right, Tab Stash will naturally also stop working.

Please try the steps here to see if it helps: https://github.com/josh-berry/tab-stash/wiki/Restart-Firefox-Without-Saved-Session-Data

If you're still having trouble, please see https://josh-berry.github.io/tab-stash/support.html for some more common steps to try, and feel free to open a GitHub issue if you're not able to resolve the problem.