Will Hunt

But it's valid to request a lot of *different* media? Assuming rate limits apply to the endpoint, not endpoint+mediaId?

https://grafana.half-shot.uk/dashboard/snapshot/7S272L4fNPWA411wMjHl75zwZVo3m0Xj

Having checked dmesg, i've got a splattering of: ``` [3327991.546676] TCP: out of memory -- consider tuning tcp_mem [3327991.721380] TCP: out of memory -- consider tuning tcp_mem [3327996.029829] TCP: out...

Forensics reveal that my TCP stack was using 4.6GBs of memory, which is definitely no-no territory. Sorry for the time waste :)

Having investigated some more, it does seem to be a matrix-media-repo problem. I've experimented with stopping the matrix-media-repo process when my `node_sockstat_TCP_mem_bytes` ran high, and it immediately dropped to zero....

Docker image. Also of note, I'm now restarting the process every 6000s to just keep it working: 

This continues to bite. Possibly related is the regular requests for ``` 2022-06-06 23:24:09 Replying with result: *r0.DownloadMediaResponse &{ContentType:image/jpeg Filename:xmas-pooch.jpg SizeBytes:18375015 Data:0xc004d70380 TargetDisposition:infer} 2022-06-06 23:24:09 Returning minimal media record with...

As a counterpoint, so far we've only seen bans from virtual Twilio numbers on emulators but real numbers have been safe.

It may be worth checking to see if your user regex in your registration file matches https://github.com/matrix-org/matrix-appservice-slack/blob/develop/config/config.sample.yaml#L30, as that would cause the error linked. The logs also indicate that you...

I'd call it a documentation bug, given this could probably be solved with more specific language