Re: SessionStore size - Bloat in sessionstore.js from Google and others causing major UI freezes

> e) Push the processing of the per-tab data over to a background
> =A0 thread/process.
>
> =A0 May play into work with Electrolysis. =A0Not necessarily at odds with
> =A0 other options above. =A0Fetching data from each tab would be the
> =A0 primary UI-blocker,

IMO, that's not really OK long term (e10s-term) -- the tabs will need
to report their state back to chrome, so that the blocking goes the
other way.

> Others? =A0Any ideas out there?

File-per-tab containing all the data for that tab, maybe?  Or two
files per tab, to avoid re-writing the big sessionstorage data every
time, if it doesn't change that often.  This would let us write out
the current tab more frequently than background tabs, as well.

Mike