Related crash reports: https://crash-stats.mozilla.com/report/index/bp-2aa28c01-048b-49cb-87ba-e7f5d0171221 https://crash-stats.mozilla.com/report/index/bp-4415b352-f6bf-4a4f-bd43-bfe400171221 https://crash-stats.mozilla.com/report/index/bp-1b8e2317-87c2-4006-8e0a-25c4c0171221

I figured out that the problem exists only if I have the "dom.indexedDB.enabled" setting set to "false" (defaults to "true"). I hope that narrows it down a bit.

Please Refresh but do this 1st:

• https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer
• https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles

then

• https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings

TEST....... If no issues then Extensions which need to be added back in 1 at a time and tested ..... Or it is your Profile : Make a new one and test ...:

• https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

If is your Profile :

• https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile
• http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox

Note: Any customization will revert back to default, you will also need to reinstall Extensions.

Suggest turning on open Gl in Video Card Drivers.

• https://wiki.archlinux.org/index.php/Firefox/Tweaks
• https://askubuntu.com/questions/491750/force-enable-hardware-acceleration-in-firefox

Please let us know if this solved your issue or if need further assistance.

It is definitely a problem with IndexedDB as you can see by the signature.

• Firefox 57.0.1 Crash Report [@ IPCError-browser | IndexedDB CheckPermission 1 ]

Any special reason that you have disabled IndexedDB as this isn't recommended?

This thread is what prompted me to disable IndexedDB: https://superuser.com/questions/1250944/how-can-this-website-reidentify-me-even-after-deleting-all-of-my-browsers-histo

Unless that behavior has changed, I'd prefer to keep IndexedDB disabled if possible.

There is the Storage Inspector if you want to see what a website stores in local storage.

• https://developer.mozilla.org/en/Tools/Storage_Inspector

You can modify and disable a lot of settings via about:config, but you can break Firefox on websites when you do so. There is a reason you get a warning when you open about:config and you should remember that.

• general.warnOnAboutConfig

Local storage like IndexedDB follows the same permission rules as set for cookies, so if you allow cookies for a website then you enable other types of storage as well (session storage and permanent storage folders in your profile folder).

Wait, what?

• You cannot turn off IndexedDB in regular browsing mode without YouTube triggering this crash, but
• Firefox automatically disables IndexedDB in private windows, where you can use YouTube without getting this crash?

What is going on there?!

Is Firefox handling the site's attempt/failure to access the database in a different (and in regular mode, far less graceful) way?

Or could YouTube be behaving differently in private windows because of either:

(A) Tracking Protection feature blocking something on YouTube (by default, Tracking Protection is enabled only in private windows), or

(B) Do Not Track signal modifying the site's behavior (by default, Do Not Track is only sent when Tracking Protection is applied)

Do you have the default settings there (Preferences page > Privacy & Security)?

I would experiment with this by toggling these settings but... I don't enjoy crashes. ;-)

In a private browsing mode window Firefox will use in memory storage, so maybe that includes IndexedDB silently??