YoursFunny 053ae0ec25 fix(send): charge the photo download window to the memory budget ...

A non-photo body charged the process-wide budget for as long as download_to_temp held it; a photo charged nothing until its prepare step, so the download itself — up to MAX_PHOTO_DOWNLOAD_BYTES per item, six items per batch, eight prep slots process-wide — was memory the MEMORY_BUDGET comment promised was bounded but was not (~6x32 MiB on top of the accounted512 MiB). Photos now reserve their own download cap for that window; the prepare step still charges header probe + decode buffer, the only overlap that is actually held in memory together. Net accounting stays within the declared budget instead of exceeding it whenever a batch of large photos downloads at once (audit: upload.rs photo window uncharged).

2026-09-24 15:29:17 +08:00

..

x-media

refactor(download): fold apply_media_headers into media_request

2026-09-24 04:37:54 +08:00

xmedia-bot

fix(send): charge the photo download window to the memory budget

2026-09-24 15:29:17 +08:00