User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180607135512 Steps to reproduce: 1. Had several containers setup in Firefox Beta (across several computers). 2. Firefox Beta Updated. Actual results: All my containers reset to defaults (on both my desktop and laptop). Expected results: Updating Firefox should maintain all my containers' state (names, colors, associated data).

do you use the same profile (on the same machine) and switch back and forth between Beta and Release versions (or beta and nightly)? There are some general storage scheme changes that make that problematic (as in dataloss). It's possible that could trigger a loss of container info but then you should also have lost other stored state. Due to recent changes it is unsafe to share profiles with different channels -- only forward upgrades are supported. (I don't want to debate that policy here -- lots of people are complaining and there are conversations elsewhere. Just trying to figure out if it's a related issue because I can't otherwise think of how one could lose their container data.)

I have everything configured to load separate profile for each Firefox version. I do switch between Beta/Nightly frequently (but again, separate profiles). It could be this config was disrupted. I've been away from these particular computers for a while--I'll be able to check this weekend. My work computer (in which I only have Release 60.0.2) never lost container data. But I fear this is something caused by the upgrade to Firefox 61 in FF beta. Any ideas on cloning a profile to test that theory out?' Thanks! Patrick