24.07

July 5, 2024

Memory Footprint: Revision of all memory-intensive components to resolve issues related to performance and memory usage.
In-Memory Indexing: Introduced IndexService for efficient in-memory asset registration. It addresses a design choice made to prioritize high performance when fallback images are used extensively.
Faster Encoding: up to 30% for WebP, 50% for JPEG and for 100% PNG (for specific access patterns and resolutions)
Faster Scanner: Improved performance of path traversal checks by min. 20% for large datasets

Updated Log4j to 2.26.1
The Tomcat APR/Native Connector has been removed in favor of a pure Java connector
CVE-2025-31650 Denial of Service Due to a Memory Leak Caused by Invalid HTTP Priority Headers)
CVE-2024-23672 (Denial of Service due to incomplete clean-up of WebSocket connections)
CVE-2023-46589, CVE-2023-45648 (Request smuggling caused by incorrect parsing of HTTP trailer headers)

Consistency issues encountered when importing and updating directory entries have been resolved
Significantly improved internal handling of service errors
fsi/service/health is more precise and the HEALTHCHECK in the container works more accurately
Hanging threads during shutdown have been fixed
Negative counter in System Monitor fixed
Possible User Session Overflow fixed

JVM: Reduced default RAM allocation
Many memory-intensive operations have been optimised
- In response, an in-memory indexing system was introduced, which statically registers each asset. This improves performance when dealing with large numbers of assets and enables fast queries. This index requires approximately 300MB of RAM per million assets.
- On Linux, you need to adjust the user_watcher_max system settings
Scanner: Intervals can be set
Improved support for video byte ranges
Access to static directories has been changed to status 403 instead of returning an empty response
Renderer: Optimized header handling and much faster response of 404 for non-existing assets