With SessionHistoryInParent (and fission), I had a pinned tab get stuck looping between about:blank and health.graphics/fission -- urlbar kept swapping, load/stop button kept switching. This continued for minutes (not apparently loading any content) until I opened a new tab and loaded health.graphics/fission. Trying to repro this has been unsuccessful/

Did not repro for me. And Randell said he also was not able to reproduce with 10 retries.

Jamie on matrix has seen the same thing recently

I've seen this a few times lately when:

1. Trying to switch channels on Slack;
2. Trying to switch views on Twitter (e.g. changing from Mentions to Notifications);
3. In combination with bug 1668920, where I get a "Temporary error" from Gmail and try to reload Gmail to fix it, at which point Gmail sometimes gets stuck in this redirect loop.

These were all with pinned tabs. Since I disabled Fission, I haven't seen this (and I was seeing it multiple times a day before).

See duplicate bug. I can reproduce this reliably by selecting 5 not already loaded tabs and then refreshing.

This also makes the whole browser chrome flicker, up to white flashes of the whole browser window.

This is still very much an issue for me.

We tried and couldn't reproduce it. Would you be able to tell us which URLs you have in those 5 tabs so we can try with those too?
And also could you try with a fresh profile?

Moving to M7 as we are still waiting for more information to debug this further.

Peter experienced this today with the SHIP google sheet which was looping between about:blank and the sheets URL and then eventually resulted in a google error page for clearing cookies and cache and retry.

Without STR, there isn't much to go on here. Punting this to M8 unless someone sees this again and has STR.

No joy trying to reproduce this yet. Let's put this in MVP to ensure we confirm before shipping Fission everywhere.

Closing as incomplete because no one could reproduce it and the session restore code has been rewritten since this bug was filed 10 months ago.

If anyone sees this bug again, please reopen this bug or needinfo me here.