Element call regularly gets stuck on "Loading..." screen.

[erikjohnston]

Steps to reproduce

1. Open an element call link. This happens fairly reliably.
2. Get stuck on "Loading..." screen
3. Refreshing often (but not always) takes you to the "enter display name" screen. Then you can join the call as normal.

The console logs from the loading screen ends with:

logger.ts:48 Error downloading keys for @aqua-electoral-jackal:call.ems.host: DOMException: The user aborted a request.
(anonymous) @ logger.ts:48
logger.ts:48 Error downloading keys for @aqua-electoral-jackal:call.ems.host: DOMException: The user aborted a request.
(anonymous) @ logger.ts:48
/room/#/backendprodu…A5gl0TsSEtRiAvUJ2:1 Uncaught (in promise) DOMException: The user aborted a request.
logger.ts:48 Error: Crypto store data was expected, but none was found
    at kR (matrix-utils.ts:134:37)
    at async Qze (ClientContext.tsx:374:24)

Outcome

What did you expect?

To be able to join a call

What happened instead?

It gets stuck until you refresh

Operating system

Ubuntu

Browser information

Chrome Version 116.0.5845.187 (Official Build) (64-bit)

URL for webapp

call.element.io

Will you send logs?

No