Tree style tab doesn't work after updating to version 2.4.8.
NOTE: starting with a clean profile does not apply because this problem happens when updating the extension.
TST reloads in a working state, with my tree restored.
The TST sidebar opens, but it's just a white dot bouncing left and right on a gray background.
More details. It seems that TST 2.4.8 has broken behaviour with regards to containers. If I disable these extensions:
Then TST can reload and "works". HOWEVER it loses all my windows and containered tabs. Only a very limited number of them can be salvaged from Firefox's "Recently closed tabs" and "Recently closed windows".
And if I enable those extensions again, TST stops working (the tree disappears from the TST sidebar).
Possible duplicate of #1735?
Maybe. Even the workaround described in #1735 seems not very reliable though; I had to retry it a couple of times for the tree to load. And then I get these ugly, red-dot borders around the elements in the tree. Is there a way I can get rid of those borders?
I've tried with these steps:
But I couldn't reproduce any problem. There are possibly some more triggers around configs of those addons. @ksze Did you check "Always open in Default" for any domain, at the popup menu of Firefox Multi-Account Containers?
@piroor No, I don't have "Always open in Default" (or "Always open in
It's pretty recurrent, infinite loading like that.

For all: could you cooperate to research what happens when the "infinite loading" happens? Steps to research:
gMetricsData.toString().The last step reports a details of the initialization process successfully. If the sidebar is correctly loaded, the log will be:
total 2600 msec for 57 tabs
0: Loaded
632: init start
247: browser.tabs.query, configs.$loaded
570: applyStyle, waitUntilBackgroundIsReady and retrieveAllContextualIdentities
1: getEffectiveWindowCache start
12: (async) calculateDefaultSizes
5: (async) initializing contextual identities
2: (async) tabContextMenu.init
289: (async) getting kWINDOW_STATE_SCROLL_POSITION
396: getEffectiveWindowCache get {"cache":false}
6: getEffectiveWindowCache fail
402: (async) read cached sidebar contents
392: (async) getting registered addons and scroll lock state
153: rebuildAll (from scratch)
471: inheritTreeStructure: kCOMMAND_PULL_TREE_STRUCTURE
1: applyTreeStructureToTabs: start
0: applyTreeStructureToTabs: preparation
27: applyTreeStructureToTabs: attach/detach
11: applyTreeStructureToTabs: collapse/expand
1: inheritTreeStructure: applyTreeStructureToTabs
509: (async) inheritTreeStructure
0: start to listen events
49: apply configs
1117: (async) main
1103: (async) parallel initialization tasks
5: applying scroll position
30: init end
On the other hand, on such "infinite loading" case, the result will become too short and some part will be missing. So it helps me knowing what process failed on the case.
I did what you've said and got this:

In "Select an iframe as the currently targeted document" selected sole "/sidebar/sidebar.html", idk why there is "background" in window title
I personally suspect there is something racy in FF WebExt tabs load code, sometimes TST loads normally, but most of the time - not
Edit: oh, didn't see this info already have been provided in other issues...
@RanHum Thanks a lot! Your log is quite similar to other logs from contributors, so they all may see same problem. Now this issue is quite same to #1735, so I close this as a duplicated. For further research, could you cooperate to collect detailed logs on the startup process? Steps to collect logs are:
/sidebar/sidebar.html?... from the namespace selector of the remote debugger, and run a script log.logs.join('\n') in the console. Then you'll see recent 1000 logs, so please paste it to #1735.
Most helpful comment
@RanHum Thanks a lot! Your log is quite similar to other logs from contributors, so they all may see same problem. Now this issue is quite same to #1735, so I close this as a duplicated. For further research, could you cooperate to collect detailed logs on the startup process? Steps to collect logs are:
/sidebar/sidebar.html?...from the namespace selector of the remote debugger, and run a scriptlog.logs.join('\n')in the console. Then you'll see recent 1000 logs, so please paste it to #1735.