Image transforms buffer originals twice and have no decode limit
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- aws, azure, csharp
- Domain
- backend, performance
Research direction
Start with MediaTransforms.cs around lines 159 and 179, then trace the full-size decode in SkiaImageProcessor and the AI alt-text path that shares it. The proposal names several coordinated changes, including buffering, single-flight requests, a decode semaphore, and downscaled decoding. Done means concurrent requests for one cold variant decode once and decodes are capped per instance.
Written by the indexing model from the issue text.
Description
Problem
MediaTransforms.RenderAsync (MediaTransforms.cs:159,179) opens the source twice; on S3 and Azure each open buffers the whole file. The full-size decode in SkiaImageProcessor allocates up to about 200 MB at the default MaxSourcePixels, and nothing caps concurrent decodes or deduplicates requests for the same variant, so a burst of first visits can exhaust memory. The AI alt-text path uses the same code.
Proposal
Use the stored dimensions instead of the first read, spool non-seekable sources once to a temporary file, single-flight per variant, a global decode semaphore, and decode downscaled when the target is much smaller.
Acceptance
- Concurrent requests for one cold variant decode once
- Decodes are capped per instance
Found in the code review of 17 Nov 2026 (P2).
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100