my element has queued up 12 requests to GET /publicised_groups

[richvdh]

... which means that no other requests are going through. could it cancel them after a while rather than letting them stack up indefinitely?

[richvdh]

It's rubbish that synapse blocks for so long, but the client shouldn't just stack them up infinitely.

this waterfall might illustrate the problem: note the overlap in requests:

[t3chguy]

Well presumably it should not do it in an interval but with a given period between requests

[turt2live]

I can't find the issue now, but this also applies when the media repo is slow/overwhelmed: switching rooms can cause a ton of media requests to start up, blocking requests, therefore preventing sync, and starting a death spiral.

Edit: usually these are thumbnails or url previews -> #10555 #7292

[richvdh]

Given that /publicised_groups is no longer a thing, presumably this is fixed.