Steven 8f29db2f49 fix(server): prevent memory exhaustion in thumbnail generation ... Address high memory usage when opening resource tab (fixes #5183) by implementing: 1. Concurrency control: Limit thumbnail generation to 3 concurrent operations using semaphore to prevent memory exhaustion when many images are requested simultaneously 2. S3 optimization: Skip server-side thumbnail generation for S3-stored images by default. S3 images now use presigned URLs directly, avoiding: - Downloading large images from S3 into server memory - Decoding and resizing images on the server - High memory consumption during batch requests 3. Memory management improvements: - Explicitly clear blob and decoded image from memory after use - Restructure thumbnail cache check to avoid unnecessary semaphore acquisition - Double-check pattern to prevent duplicate generation while waiting This restores the original S3 behavior before commit e4f6345 while maintaining thumbnail support for local/database storage. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>		2025-11-07 09:04:21 +08:00
..
profiler	chore: fix linter	2025-05-27 23:22:32 +08:00
router	fix(server): prevent memory exhaustion in thumbnail generation	2025-11-07 09:04:21 +08:00
runner	refactor: rename workspace to instance throughout codebase	2025-11-05 23:35:35 +08:00
server.go	refactor: rename workspace to instance throughout codebase	2025-11-05 23:35:35 +08:00