aboutsummaryrefslogtreecommitdiff
path: root/Emby.Server.Implementations/Localization/Core/ht.json
diff options
context:
space:
mode:
authorvavallee <vavallee@protonmail.com>2026-08-07 12:33:37 -0300
committervavallee <vavallee@protonmail.com>2026-08-07 12:33:37 -0300
commite120b7f2dd986d7f07f6814b6d987bafd46baab8 (patch)
tree341f66983ebd0d6972755064f53925674bc96a2e /Emby.Server.Implementations/Localization/Core/ht.json
parent6c37a6ef8b4ce027e7ac2aaa827244711cf5f39c (diff)
Stop image endpoints from upscaling beyond the source resolution
ImageHelper.GetNewImageSize passed the caller-supplied width/height straight through to SkiaEncoder.EncodeImage, which allocates an SKImageInfo of exactly that size. Nothing bounded those values against the source image, so a request like Items/<id>/Images/Primary?width=23100&height=23100 made the server allocate and resample a 23100x23100 surface from, say, a 600x336 poster: the reporter measured 100% of a core for 10-15 minutes and 6-12 GB resident per request. The item images endpoints do not require authentication, so any caller who knows an item id can trigger this, and varying the size by one pixel misses the cache every time. Add DrawingUtils.ScaleDownToFit, which scales a size down uniformly until it fits inside a bounding box and returns it unchanged if it already does, and apply it in GetNewImageSize against the original image dimensions. Requests that ask for more pixels than the source now get the source resolution back, scaled to the requested aspect ratio. Downscaling paths are untouched, and DrawingUtils.Resize keeps its existing behaviour for the transcoding callers in EncodingJobInfo and StreamInfo, which legitimately size video output. ResizeFill already refused to upscale; this makes width/height consistent with fillWidth/fillHeight. Fixes #17056.
Diffstat (limited to 'Emby.Server.Implementations/Localization/Core/ht.json')
0 files changed, 0 insertions, 0 deletions