oooh yes, it feels so good to painlessly close tabs again.
Few observations:
When I tried to disable the plugin for the first time, several assertions were thrown, that caused CB to be unresponsive. Unfortunately, I haven't noted them.
After a restart of CB, the plugin was disabled and tabs could be closed without issue (yay).
Again I tried to enable the plugin (no problem), and tabs were still closing without the issue.
Next, I restarted CB, the plugin was enabled and issue with tabs was present again. However, this time disabling the plugin was without assertion errors and issue with tabs disappeared again.
So TL;DR
If you want to use BrowseTracker plugin, disable and enable it on every start of codeblocks. Otherwise, keep it disabled.