X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

indexedDB Unkown Error

Kuphostiwe

I'm working with a private system webpage (only a minor set of people may see it). Since I updated firefox to firefox 35, it has been showing the error:

"IndexedDB UnknownErr: ActorsParent.cpp:412"

This also happens in safe-mode and if I turn every extension off.

In the only bugzilla bug I could find, it was set as fixed. ( https://bugzilla.mozilla.org/show_bug.cgi?id=1093223 "IndexedDB UnknownErr: ActorsParent.cpp:413" on indexedDB.open)

Firefox 35 has been out for some days now, so I believe if this was an actual bug it would already had been reported.

How do I solve this error?

Meanwhile, I'm rolling back to version 34.

I'm working with a private system webpage (only a minor set of people may see it). Since I updated firefox to firefox 35, it has been showing the error: "IndexedDB UnknownErr: ActorsParent.cpp:412" This also happens in safe-mode and if I turn every extension off. In the only bugzilla bug I could find, it was set as fixed. ( https://bugzilla.mozilla.org/show_bug.cgi?id=1093223 "IndexedDB UnknownErr: ActorsParent.cpp:413" on indexedDB.open) Firefox 35 has been out for some days now, so I believe if this was an actual bug it would already had been reported. How do I solve this error? Meanwhile, I'm rolling back to version 34.

Okulungisiwe ngu brunoais

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Adobe PDF Plug-In For Firefox and Netscape 11.0.10
  • Version 3.10.2.10212
  • Intel web components updater - Installs and updates the Intel web components
  • Intel web components for Intel® Identity Protection Technology
  • Next Generation Java Plug-in 10.71.2 for Mozilla browsers
  • Shockwave Flash 16.0 r0
  • VLC media player Web Plugin 2.1.0

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows; Windows NT 6.1; Win64; x64; rv:36.0) Gecko/35.0 Firefox/34.0

Eminye Imininingwane

FredMcD
  • Top 10 Contributor
4339 izisombululo 61020 izimpendulo
Kuphostiwe

I've called the big guys to help you. Good luck.


Start Firefox in Safe Mode {web link} While you are in safe mode;

Type about:preferences#advanced<Enter> in the address bar.

Under Advanced, Select General. Look for and turn off Use Hardware Acceleration.

Poke around safe web sites. Are there any problems?

I've called the big guys to help you. Good luck. ---------------- '''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Start Firefox in Safe Mode]''' {web link} While you are in safe mode; Type '''about:preferences#advanced'''<Enter> in the address bar. Under '''Advanced,''' Select '''General.''' Look for and turn off '''Use Hardware Acceleration'''. Poke around safe web sites. Are there any problems?
cor-el
  • Top 10 Contributor
  • Moderator
17771 izisombululo 160723 izimpendulo
Kuphostiwe

Make sure that the dom.indexedDB.* prefs have the default value on the about:config page.

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

Make sure that the dom.indexedDB.* prefs have the default value on the <b>about:config</b> page. You can open the <b>about:config</b> page via the location/address bar. You can accept the warning and click "I'll be careful" to continue. *http://kb.mozillazine.org/about:config

Umnikazi wombuzo

In about:config for IndexedDB, all values are the default.

In '''about:config''' for IndexedDB, all values are the default.
philipp
  • Top 25 Contributor
  • Moderator
5345 izisombululo 23602 izimpendulo
Kuphostiwe

can you try if the same problem is happening in firefox 36 beta. (the bug from the report you have mentioned should be fixed there): https://www.mozilla.org/firefox/channel/#beta

can you try if the same problem is happening in firefox 36 beta. (the bug from the report you have mentioned should be fixed there): https://www.mozilla.org/firefox/channel/#beta
guigs 1072 izisombululo 11697 izimpendulo
Kuphostiwe

Impendulo Ewusizo

The mentioned bug looks like it will land in version 36. This is the current beta version. Does this error still happen in beta? If so, it is possible to reference this bug in a new one or make a comment on the bug with mention of all the troubleshooting already done. With in mind the etiquette

The mentioned bug looks like it will land in version 36. This is the current beta version. Does this error still happen in beta? If so, it is possible to reference this bug in a new one or make a comment on the bug with mention of all the troubleshooting already done. With in mind the [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html etiquette]

Umnikazi wombuzo

Ups. I lost the e-mail warning about the other post.

Anyway, I've just tested on firefox 36 beta 1. It is still not solved. I don't think that there's any filed bug about this specific one, so I'll file a new one.

Ups. I lost the e-mail warning about the other post. Anyway, I've just tested on firefox 36 beta 1. It is still '''not solved'''. I don't think that there's any filed bug about this specific one, so I'll file a new one.

Okulungisiwe ngu brunoais

Umnikazi wombuzo

Done: reported, https://bugzilla.mozilla.org/show_bug.cgi?id=1124189
philipp
  • Top 25 Contributor
  • Moderator
5345 izisombululo 23602 izimpendulo
Kuphostiwe

thank you, it looks like it's making good progress there!

thank you, it looks like it's making good progress there!

Umnikazi wombuzo

Thanks. As a programmer myself, I have some ideas on how things work :D.

Thanks. As a programmer myself, I have some ideas on how things work :D.