GSD won't load, even offline version

[bartveld]

Every now and again GSD will not load, usually when going back from another page. Trying to load the offline version doesn't work either. I get this report:

Environment: Web - Group Speed Dial ☁️ 29.4; name: web, version: 151, userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:151.0) Gecko/20100101 Firefox/151.0; os: win, arch: x86-64;
Background script state: ✅ ok
Missing API: 🛑 [<all_urls>]
💾 indexedDB: 286.0 MB, storageLocal: 21.2 KB, storageSync: 2.0 B, storageSession: 750.0 B, localStorage: 554.0 B, sessionStorage: 43.0 B, quota: 931.1 GB
Sync status: synced
Pixel ratio: 1
Running time: 63s
Stats: 0 -
🗨️ Runtime logs:
30. 05. 2026 12:19:11 -41ms, clou, System: store ready
30. 05. 2026 12:19:11 60ms, clou, System: First tab starts loading.
30. 05. 2026 12:20:04 52705ms, clou, System: First tab starts loading.
30. 05. 2026 12:20:14 10012ms, clou,🛑 System: Background init failed! |
AbortError: A request was aborted, for example through a call to IDBTransaction.abort.

Restarting Firefox usually solves it, but it's like Firefox and GSD don't play nice anymore. Not a big problem, but just wondering what is causing it.

Device info:
Windows 11
Firefox 151.0.2

• GroupSpeedDial version: 29.3

[Juraj-Masiar]

Hello,
First of all, it seems you are using Cloud Dials webpage, not the extension (add-on), so things can break more easy since web technologies are more fragile than native extension.
More info:
https://github.com/fastaddons/GroupSpeedDial/wiki/Cloud-Dials-web-page
Also, the Cloud Dials is not exactly "offline version", it may work a bit, but I doubt it would initially load without internet. Only installed extension will work "ok" without internet.

In any case, it looks like some database issue (IndexedDB), sadly since Firefox 149 there is a lot of database issues reported.
And I have feeling Firefox team is now quite busy fixing security issues that modern AI models are finding.

Oh... checking the Cloud Dials on my own PC, I see it actually fails to open too!
It works again right after refreshing the page, but the initial load shows only black screen.
And checking it moments later... it failed again!
And checking it one more time - this time it loads but it took many seconds to load - this is very likely database related since initial dials drawing is completely offline operation.

This is bad, and I see also the same database error in the console:

Uncaught (in promise) DOMException: A request was aborted, for example through a call to IDBTransaction.abort.

OKOK, the good news is, I can reproduce it somewhat here, even with rapid reloads I can crash it.
And checking Firefox bugs tracker, it seems the same database error has been recently reported:
https://bugzilla.mozilla.org/show_bug.cgi?id=2016379
https://bugzilla.mozilla.org/show_bug.cgi?id=2026186

I'll investigate, thank you for reporting this!

[bartveld]

Well, in a sense I'm glad it's happened to you too. One thing though: I am using the extension, never heard of the Cloud Dials webpage option.

[Juraj-Masiar]

Well, the error logs you've pasted here are definitely coming from the cloud:

Environment: Web - Group Speed Dial ☁️ 29.4

Could you open Firefox settings page:
about:preferences#home
And verify that both of these options are set to "Group Speed Dial":

[bartveld]

New Windows is set to google calendar. New Tabs to Group Speed Dial

[Juraj-Masiar]

So how did you end up on the Cloud Dials website?
How do you open your dials page?
Because if you open it through a link like this:
https://group-speed-dial.fastaddons.com/cloud/
Then you end up on a Cloud page, not the extension page, which doesn't have a visible link (URL), but internally it looks something like moz-extension://bdf368b4-8e8f-465a-9ac5-5517a6d89311/dial.html.

[bartveld]

Ouch. Of course you're right. I set New Windows to GSD and there it is:

as opposed to the old situation:

I apologize for my ignorance and thank you for taking the time to set me straight on the basics.

[Juraj-Masiar]

It's fine, don't worry about it. I definitely need to make more videos that would explain al these concepts.

And I'm supper happy I can finally reproduce the database issue!
Now I need to prepare some simple code that triggers the issue and then send it to Firefox team for fix.

UPDATE:
Bug reported to Firefox team with easy to reproduce steps:
https://bugzilla.mozilla.org/show_bug.cgi?id=2044020