Not I originally wasn't going to give a review for this extension, because it's ultimately Mozilla's fault that Tile Tabs WE is utterly useless and not even a shell of its former self (and because giving 1/5 for reasons that are clearly out of author's control is ultimately a douche thing to do). I planned to install this extension, just in case FF decides that some of its deprecated functionalities make a comeback under WebExtension API. At the end of the day — while the original ability is going to be sorely missed — the current implementation is infinitesimally better than nothing despite being less than ideal.

Unfortunately though, when recovering from a crash (but not if firefox was shut down or restarted properly, even if it's set to reopen my previous session) at nearly 300 tabs across three windows, this extension manages to:

* Completely freeze firefox for a couple of minutes (100% cpu usage on a single core)
* RAM usage flunctuates wildly during the startup, but the peaks go past 10 gigs (!!) for me with my 3 windows and just shy of 300 tabs.
* After the dust settles and Firefox opens and becomes responsive again, RAM usage stabilizes at 5 gigs for what used to be less than one

With 16 gigs of RAM in my machine, such RAM usage is enough to surprise-crash my entire machine if I have other things running as well.

This only happens when this extension loaded. If it's disabled, everything is normal. (Although this could potentially be a conflict with Tab Mix Plus and Multiple Tab Handler, both of which are also going away). FF56, linux. Not sure whether that's firefox or some extension, but tabs are set to not load until I visit them.

If you're the kind of person who shuts down firefox and computer in ways that result in "do you want to restore your last session" message and your tab count is in triple digits because tab bar is the new bookmarks, you should probably avoid this extension for the time being.

So that's the reason for 2/5. When extension crashes my machine with OOM ...

There's also other wonkiness that might not be dev's fault, but:

* if firefox is fullscreen (the "I can still see the window titlebar and taskbar" kind of fullscreen, not f11 kind of fullscreen), on my main (middle) monitor and I try to split the window, the two new split windows appear on my secondary (leftmost) screen. (This could potentially be the fault of kwin). Surprisingly enough that doesn't happen when firefox window doesn't take up the whole monitor.




P.S. Thanks a lot moz, FF56 is the new Opera 12.16