Renaming a second time causes Chrome to loop.

[AugustM]

When I use RenameTab with a site that regularly updates its title, l ike Facebook, which included a number for unread notifications, if I just use the normal "Rename Tab" button, the title will change back at some point, before I'm done with that tab. So I use the "Lock TItle (beta)" button.

I've found this so useful that I've written a hotkey macro to change the tab title to the text selected on the page. That works great ... UNTIL ... If I accidentally use that hotkey to attempt to rename and lock the title of a tab that has already been locked, Chrome goes into a loop where it flips the tab title back and forth rapidly. That begins to consume a lot of CPU resources. If I notice it in time and can close the tab some other way, like in one of my tab managers, I'm usually OK, but if I don't notice and loop goes for a while, it can lock up Chrome to where the only solution is to kill Chrome -- which sometimes means losing a bit of unsaved work.

This is a painful bug. Yes, it can be avoided by a simple, "So don't do that", but accidents happen.

[alexbate]

Thank you for your interest in RenameTab and for reporting this bug, but I'm afraid I'm no longer able to maintain the extension. The code is open source and welcome to be forked.