This is actually looks like a scenario that i have in mind. Needs wait for a next release, i try to fix this in it. 

What is OS and Chrome version by the way?

Most likely it is the same problem. Close a duplicate for now

Sorry guys, was very busy to publish some fixes. Yet i am really surprised that you experience this so severe.

I am actually never be able to reproduce this, i have only theoretical ideas how this potentially might happens (yep yes, there is real problem in code in this regards, and i have idea how to fix, but i really never experienced its on any of my testing platforms)

Can you mention some links maybe where this happens most of the time, your OS and Chrome version.

Also how this happens - do you enter by hand some text in address bar before this? The exact scenario of what are you doing will be very helpfully. As it might be not what i think at all.

maybe you can reproduce this problem and record a screencast of this using some of the free services:

like:

http://www.screencast-o-matic.com/

or

http://www.screenr.com/

this will be helpful i think

Chrome have native flash block (click to play) abilities by the way, read the advice of how enable it in the Tabs Outliner help, the last item in the "Some useful tips" section  : ) 

Works for me much better than the external tools.

By the way, for a what forums you talk?

You cannot participate there in discussions?

Seems it is time to change the feedback system provider, from time to time there is such complains... 

From version to version there is a progress in this regards actually. Next version will have even lower memory usage. But some limits just very hard to overcome. Take note that sometimes even the simplest web pages consume dozen of megabytes of ram in the Chrome. It is well famous for this feature : )

The 250 MB memory consumption can be real. If you have something around 15 000 saved nodes. Next version will reduce this, but not on a magnitude.

My advice for now, if you have many thousands nodes (note that other extension just cannot even come close to such counts of simultaneously visible nodes) and the ram consumption is a big issue for you - expand all nodes, save the tree as a plain text web page (through Ctrl-S). 

Check if this page is rendered ok (reopen it in some tab)

Then uninstall Tabs Outliner - this will delete all its data (WARNING!!! THIS WILL DELETE ALL ITS DATA!!! RE READ THIS). Then install it again and start your tree from scratch. This will return you ram usage to 10-15MB. 

Use your saved in html tree to access  for old data (you can drag from it back to main view some individual windows and groups by the way). 

Other solution - having most of the part of tree collapsed - if items is collapsed it is not rendered in HTML, and consume very little ram. But it is actually more useful to have your old tree as a separate web page.

There is some price that need to be paid for some features. If you have a lot of data visible on screen in HTML world this is unfortunately lead to a big memory usage. In fact - if you continue to grow your tree indefinitely the ram usage will continue to grows also, you can reach any digits that you want this way. So you need decide what is more important for you - the ram, or having all the data in one tree.

I am periodically (once in 6 months actually) drop the whole tree in a file and start from scratch. Soon there will be better way for a same - it will be possible to create separate tree documents. So all the data will continue to be searchable and editable (the tree in a static HTML file is not editable by drag and drop... but editable in any HTML editor by the way)

Best.

How many saved nodes do you have in your tree?

(this can be measured by collapsing the root node temporary)

Unfortunately, this is a most common request, yet it cannot be done now because of the Chrome limitations. It's impossible meantime to restore back and forward history from extension. So there is no any extension in the Chrome Store that can do so.

The Chrome API's to support this are currently in development. I plan to take advantage of them as soon as they're complete.

To monitor its progress please stare there issues:

https://code.google.com/p/chromium/issues/detail?id=41321&can=1&q=restore%20tab%20history%20from%20extension&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified

https://code.google.com/p/chromium/issues/detail?id=14737&can=1&q=restore%20tab%20history%20from%20extension&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified

Please stare them anyway, this will help to raise their importance for a Chrome team.

Meantime work on synchronization but for future version is planed a context menu with an entry for a such functionality, and a bunch of related.

So you restore you window and instead of restoring only the open tabs last time it is restore everything.

There is not first time i hear such request, And there is special alternative restore specially for people with such requirements : ) 

Try restore the window by Dbl-click with ALT button pressed.

This will restore only the tabs that was open last time you save the window.

This hidden feature is not mentioned in help : )

Best.

why someone down-voted is a really interesting question : )

That seems human nature for somebody.

As for request to automatically unload tabs i prefer not to overweight the tool by the rarely used functionality which can be done as separate extension.

There already such addons - The Great Suspender, Tab Mem Free, to name a few. I was tried them shortly and don't find them very useful actually. Anyway such addition must be done as separate extension. It might communicate with TO to save tabs inside it. But i prefer not to add this functionality to the TO itself.

There is already enough people who down vote because it's to complicated for them.