element-hq / element-hq/element-web

Rageshake appears to require a healthy/online homeserver

Open
#23,955 0 comments 0 reactions 0 assignees View on GitHub
A-Performance O-Occasional S-Minor T-Defect Z-Rageshake
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Have a homeserver that is online but extremely slow
2. Try to submit a rageshake

### Outcome

#### What did you expect?

A bug report to be sent

#### What happened instead?

![image](https://user-images.githubusercontent.com/1190097/206770114-e8d49aff-2e7f-4fe3-81f0-e17c9ab7dcdf.png)

for eternity

My best guess is the http request(s) are getting stuck in a large queue, as the client is stacking them up. Further, if the server is down, then this happens:

![image](https://user-images.githubusercontent.com/1190097/206770247-6eeb37bd-e4cc-40fa-8525-ac4dace3971c.png)

### Operating system

Windows 10

### Application version

Element Nightly version: 0.0.1-nightly.2022120901 Olm version: 3.2.12

### How did you install the app?

The Internet

### Homeserver

t2l.io

### Will you send logs?

Yes

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.