Sorry to hear about the crashes and thank you for the report ID.

Something went very wrong when Firefox was loading that page or PDF: according to the online version of the crash report, it requested over 9MB of memory and when Windows failed to make that available, it crashed with an out of memory error.

It's hard to picture what kind of web content requires that much memory (other than a video). Certainly a normal monthly statement isn't that big.

I no longer have a Sprint login, so I don't know whether it's possible to simply save the PDF first before trying to open it in Adobe Reader. Is there a link you can right-click and Save Link As to download the PDF?

Regarding printing to PDF, do any other sites crash Firefox when you try to do that, or only Sprint's site?

Thanks jscher2000. -I was trying to open the PDF in Adobe; but, Sprint Requires it to open in Firefox before you can 'download it to Adobe'. So, that means I could not try it exactly the way you suggested it. -I have not tried it on another website yet (it took me literally hours to get the pdf file to download finally; and, even then, Firefox crashed - I just happened to beat Firefox to the punch and get the pdf to open in Adobe.) -The size increases when it is saved to disk from Adobe. The file when opened in Firefox in the past has been about 450 kb. The file saved after Adobe is 1.6 MB.

Firefox just updated to 49.0 yesterday (Sunday). So, I haven't had a lot of time to test/stress it yet. -Still, I can already tell that 49.0 is running very slow - so, I would bet the problem is in 49.0. I never had this problem in any other version of Firefox doing exactly the same thing (both the slowness and the PDF opening on the Sprint site.) -I believe that Firefox needs to check some things because there are problems in 49.0.

To bypass having to review PDFs in a Firefox tab, try changing your PDF setting to "Always Ask" on the Options page. This article points the way to the setting: View PDF files in Firefox or choose another viewer.

Regarding performance, one of the headline changes in Firefox 48 was that some users have a new feature enabled (e10s), which separates the browser interface process from the page content process. The content process moves into plugin-container.exe. Firefox 49 is expanding the roll-out, so this might cause issues for some users.

Could you check whether you have this feature turned on? Either:

• "3-bar" menu button > "?" button > Troubleshooting Information
• (menu bar) Help > Troubleshooting Information
• type or paste about:support in the address bar and press Enter

In the first table on the page, check the row for "Multiprocess Windows" and see whether the number on the left side of the fraction is greater than zero. If so, you are using e10s.

If your Firefox is not performing well with e10s enabled, you could try turning it off here:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.

(2) In the search box above the list, type or paste autos and pause while the list is filtered

(3) Double-click the browser.tabs.remote.autostart.2 preference to switch the value from true to false

Note: the exact name of the preference may vary, but it will start with browser.tabs.remote.autostart

At your next Firefox startup, it should run in the traditional way. Let us know if you notice any difference. (It's really a temporary workaround for diagnostic purposes, and not a solution.)

If you are willing to suffer a bit more, a developer has been seeking out people who see the "loading" icon on tabs to help debug the problem. More info in this Reddit thread:

https://www.reddit.com/r/firefox/comments/51t9bi/please_help_me_destroy_the_tab_switch_spinner_on/

Also, it was suggested to make a screen recording in this post: https://www.reddit.com/r/firefox/comments/54fxoj/how_to_remove_the_loading_of_the_page/d81q9uj

Thanks yet again jscher2000!

The fraction says: 0/1 (disabled by add-ons). -So, it looks like to me I do not have e10 enabled.

Also, FYI - I went into an online community of which I am a member. -Being in the community pegged by CPU and slowed down to a crawl (even typing was halting between letters.) -Yet, on last Saturday (before Firefox updated), I was in the same community opening the same windows doing the same activity - and, things worked great (and fast).

Yet again, the only change - Firefox updating to 49.0.

I applaud any suggestions/thoughts. -Thank you for those thus far. In the meantime, I will continue to monitor (tomorrow, it's time for me to shut down tonight where I am) and see what else is affected, if anything, as I go about my daily usage. -More and more - common sense logic is telling me - that is seems like there is something in Firefox 49.0 that is causing problems that did not exist. I wish, in some ways, I could roll back; but, eventually, that would leave me vulnerable in the near future if not immediately.

Again, Thanks!!! -I look forward to what else you and any others have to share.