Closed Bug 1012428 Opened 10 years ago Closed 10 years ago

Google Docs isn't working after last Nightly update

Categories

(Firefox :: Untriaged, defect)

32 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1010783

People

(Reporter: roman.rellum, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release)
Build ID: 20140518030203

Steps to reproduce:

After last Nightly update I'm unable to view any google document from google docs. It throws error at me and webpage is useless.

Error translation to english would be something like: "Browser error occured. Please hold shift and click on refresh button in order to try again."

Issue is same on two different computers. Creating new profile did not help.
Is Google Docs working if you set browser.cache.use_new_backend_temp to false via about:config ?
Summary: Google Docs crashing after last Nightly update → Google Docs isn't working after last Nightly update
Yes, it did help. What is it and is it supposed to be set to false from now on? Why it is not set to this value by default when its such critical change since I had issues with Adobe Reader plugin aswell as few other sites I've visited yesterday.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
i forgot to answer your question:
>What is it and is it supposed to be set to false from now on?

We have a new disk cache and it got enabled in that nightly. You have found a bug in this new Cache Code.
The bug is already fixed (see bug 1010783 ) and you can change the option back to the "normal" value after you downloaded a nightly after the fix got checked in.

>Why it is not set to this value by default 
You are using a Nightly build. Nightly builds are untested builds that are automatically generated each night with the newest source code changes.

This is not a critical issue for a nightly. Nightly builds can crash on startup, delete your Firefox user data (bookmarks, stored passwords....) and in theory delete your hdd if you run Firefox with enough privileges.
You need to log in before you can comment on or make changes to this bug.