FF 55 - Tabs opened during crashed session = about:blank

User Help for Mozilla Firefox
Post Reply
bluloo
Posts: 34
Joined: November 6th, 2006, 8:13 pm

FF 55 - Tabs opened during crashed session = about:blank

Post by bluloo »

Using FF 55, the day after the update.
Opening a google.com/express page crashes the browser.
Every tab that was opened in that crashed session is still present, the tab has the page description, but the URL is empty and the page doesn't load any content. Clicking on the noscript icon indicates that the page is seen as "about:blank", instead of the url open during the crash.
I know the devs work pretty hard (<3 <3) , but based on the many contents for this version, the FF update seems pretty broken and downgrading seems blocked.

Any fix that doesn't require losing everything involved in creating a new, empty profile?
bluloo
Posts: 34
Joined: November 6th, 2006, 8:13 pm

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by bluloo »

Update - it seems that about a third of my open tabs only display "about:blank". The URLs have been deleted and there's no page content.

What a horrid rollout for this version...
User avatar
GHM113
Posts: 707
Joined: December 16th, 2015, 3:59 am
Location: Moscow, Russia

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by GHM113 »

Sorry for my poor English.
bluloo
Posts: 34
Joined: November 6th, 2006, 8:13 pm

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by bluloo »

Thanks! I'm on a Mac, so hopefully the shared code is updated for both platforms.

I was also able to mitigate it somewhat by restoring a prior browsing session, w/o those about:blank tabs, via session manager.
bluloo
Posts: 34
Joined: November 6th, 2006, 8:13 pm

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by bluloo »

Still broken for me on 55.0.1...

Anyone else?
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by therube »

Says the fix should land in 55.0.2.
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Brummelchen
Posts: 4480
Joined: March 19th, 2005, 10:51 am

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by Brummelchen »

if you have a profile backup when you used v54 you should go back to v54 and that backup. sorry.
55.0.2 not in sight, neither candidate nor final, only trybuild=experimental=not recommended
bluloo
Posts: 34
Joined: November 6th, 2006, 8:13 pm

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by bluloo »

I'm on 55.0.2, and it's not fixed - after shutting down normally, some number of tabs are either about:blank or have the site name, but no url (and no content loads). I'm using Session Manager, so I have been using it to return to the last good browsing session (and have also been saving sessions manually) for now.

It's an ugly kludge, but hopefully the issue is addressed soon.
User avatar
GHM113
Posts: 707
Joined: December 16th, 2015, 3:59 am
Location: Moscow, Russia

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by GHM113 »

Did you try to update your addons?
https://bugzilla.mozilla.org/show_bug.c ... 388628#c58
I checked add-on manager and 10 add-ons had updates available. I had add-on manager install these updates and now FF55 restores the session as expected.
Sorry for my poor English.
bluloo
Posts: 34
Joined: November 6th, 2006, 8:13 pm

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by bluloo »

I have auto-update set to on, but there are no updates available for my add-ons when I check manually.

FF still re-opens with randomly empty tabs. I would prefer not to dump FF for a while, until it's fixed, but may have to go that way.
bluloo
Posts: 34
Joined: November 6th, 2006, 8:13 pm

Re: FF 55 - Tabs opened during crashed session = about:blank

Post by bluloo »

Latest update (55.0.3) seems to have fixed the about:blank issue.
Post Reply