What did you do? ================ 1. Load a webpage 2. Close it 3. Load it again What happened? ============== When all cache and local storage is cleared from FF, pages load fine. However, after an uncertain amount of loads, FF starts to fail loading the pages. Console output examples: Reddit.com: ``` .033 [Show/hide message details.] TypeError: r.sendError is not a function[Learn More] 18:16:54.150 Error running module reddit.js : TypeError: this.$el.find(...).validator is not a function reddit-init.en.xE6foQQcI8M.js:6:1815 r.logging.sendError https://www.redditstatic.com/reddit-init.en.xE6foQQcI8M.js:6:1815 <anonymous> https://www.redditstatic.com/reddit.en.vUxnTaU6k3M.js:11:27613 ... 18:20:37.828 Client Error: "TypeError: togglecomment is not a function" thrown at L1:8 in https://www.reddit.com/r/firefox/comments/8j4r1k/anyone_else_having_a_good_time_with_60/ Message: "TypeError: togglecomment is not a function" Object { tag: "unknown" } reddit-init.en.xE6foQQcI8M.js:6:1815 ``` And slack.com: ``` 18:21:51.185 NS_ERROR_FILE_CORRUPTED: messages:640 18:21:52.350 NS_ERROR_FILE_CORRUPTED: rollup-core_required_ts.0e4cf20a08b98de02e0d.min.js:1 ``` (I also noticed this on sites like trello.com and zapier.com) I'm running MacOS 10.12.6 and both FF 60 and 61.0b4(64-bit). Currently running FF 61 is Safe mode (no addons enabled), and it only took 2 attempts to recreate the bug. I can clear the errors by clearing the storage (I run `localStorage.clear(); sessionStorage.clear()` a few times in the console, and give the page a refresh). However, each time I visit the site, I run into the same problem and have to clear the storage again. What should have happened? ========================== The site's JavaScript files should have correctly ran, and the pages should have correctly loaded. Is there anything else we should know? ====================================== This problem just started happening to me when FF dropped 60 out of beta. I attempted to switch out of the beta channel, but the bug appears in both versions 60 and 61.

Hi charles.srenwick, I am trying to reproduce your issue on OS X 10.12.6 64-bit and the 3 main versions of Mozilla (release 60.0.1, beta 61.0b5, nightly 62.0a1), but I could not reproduce the errors you logged the issue for. No error got displayed while closing and reopening www.reddit.com without being logged in, but errors (different than the ones in comment 0) started showing after I logged in. The errors I found are: 1. In the new reddit page design (https://www.reddit.com/) : " An unbalanced tree was written using document.write() causing data from the network to be reparsed. " " For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing container.html:8 Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive.[Learn More] " 2. In the old reddit page design (https://old.reddit.com/) : " A call to document.write() from an asynchronously-loaded external script was ignored. " " Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive.[Learn More] sn.ashx " " Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive.[Learn More] OpenX.ashx " Can you still reproduce the issue is safe mode? If so ,can you confirm that this issue is also reproducible on a new profile. Also, it would worth to check if the same error happen on Nightly v62 (normal profile, safe mode, new profile).

I'm having difficultly replicating this bug in v61 on reddit today, both in safe mode and not. However, I can confirm slack.com's unwanted behavior in both safe mode and regular mode. After about ~5 attempts with the Test Profile, however, I cannot replicate this bug.

I have attempted reproducing the issue you are describing on Mac OS X 10.13.5, Mac OS X 10.12.6 and Windows 10 with both Reddit and Slack sites and both last beta and last nightly browser versions. Results: The same errors were repeating on each OS/browser version combination, but none of the errors you logged the issue for: 1. https://www.reddit.com/ : "An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsingcontainer.html:8" "Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively." "Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively." "Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively." 2. https://www.old.reddit.com/ : "Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored." "A call to document.write() from an asynchronously-loaded external script was ignored. conversion.js:32:374" "An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing container.html:8" "Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive." 3. https://mozilla.slack.com/ : "May-18 18:45:10.599 SOCKET-MANAGER (T027LFU12) Closing socket because #4108: unexpected socket closure" "May-18 18:45:13.961 can't ingest custom emoji ::smurf:: because it's invalid" "info() expects 1 or more arguments to be passed after the required label" Charles, I need to make sure I understand your comment 2: 1. You said that you cannot reproduce the issue on Reddit anymore (in Mozilla Beta 61). 2. You said that you can reproduce some "unwanted behavior" on Slack in both safe mode and the profile you use Mozilla usually. 3. After creating a new profile, the issues on Slack could not be reproduced anymore. Can you confirm that I understand correctly? Also, please answer some more detailed questions: 4. Which Mac OS X version are you using? 5. Which (exact) Mozilla version are you using while you reproduce the issue? 6. What is this unwanted behaviour that your are having with Slack? Please explain and/or provide the error messages. If the errors you log the issue for are not reproducible anymore, please let us know so we can close it. Furthermore, new issues could be filed on the reproducing errors. Thank you very much!

> 1. You said that you cannot reproduce the issue on Reddit anymore (in Mozilla Beta 61). Yes. This issue seems to get worse at times, and better at times. Today, I have not been able to replicate the bug in any mode on reddit.com (FFv61). However, this issue pops up so often, and on so many sites that I visit, that I have now moved away from FF as my daily driver. So it is a bit harder for me to catch it when its acting up. > 2. You said that you can reproduce some "unwanted behavior" on Slack in both safe mode and the profile you use Mozilla usually. Correct. Switching between safe mode and normal mode does not fix this problem. > 3. After creating a new profile, the issues on Slack could not be reproduced anymore. Can you confirm that I understand correctly? Correct. After quite a few attempts with a new FF profile, I could not replicate this bug with slack.com. However, the problem still persists on my normal profile. > 4. Which Mac OS X version are you using? 10.12.6 (16G1314) > 5. Which (exact) Mozilla version are you using while you reproduce the issue? 61.0b5 (64-bit). When I submitted the bug report, I attempted to switch to FF v60, and it did not fix the problem. > 6. What is this unwanted behaviour that your are having with Slack? Please explain and/or provide the error messages. Slack's webapp/website is unable to finish loading. While all the CSS and HTML seems to load, it looks like the JS gets hung up and never completes loading. The website is then stuck without any actual content, just slack's default loading view. This is all I see in the console: ``` 13:01:21.829 [Show/hide message details.] NS_ERROR_FILE_CORRUPTED: C4GMF1YG7:640 13:01:23.725 May-18 13:01:23.724 [BOOT] booted! pri:0 version:1526662407 start_ms:1526662881858 (1865ms ago) modern.vendor.432d3bafec86e11ea473.min.js:1:1005026 13:01:23.726 May-18 13:01:23.727 [BOOT] Starting incremental boot (early) modern.vendor.432d3bafec86e11ea473.min.js:1:1005026 13:01:24.347 [Show/hide message details.] NS_ERROR_FILE_CORRUPTED: rollup-secondary_a_required.14ed4d23ee13932f9574.min.js:1 ```

Was running FF again today and sites started to up act up once more. After a bit more digging, I found another bug report and this comment (https://bugzilla.mozilla.org/show_bug.cgi?id=1341070#c2). Tracking down that webappsstore.sqlite file, and renaming it to webappsstore.sqlite.corrupted, and restarting FF has completely fixed my problem. I'm not sure if that means this bug is closed, as the fix seems both too technical and unnecessary for normal FF users, but at least there is a fix (for me). Excited to use FF again. (I kept a backup for that corrupted sqlite file, in case it might be helpful to send.)

Thank you for the report! I'm happy that you found your temporary workaround. I will set this bug as duplicate of bug 1341070, because it seems like the same problem and it will be addressed there, while the details you provided here may be of use. Please reopen if it's proven to be a different one. A different type of error will need a different bug logged, please keep in mind to log different bugs for different issues. Thank you, Charles :)