Dispatcher - font files are cached with size 0 following design tree activation
When we upload a new custom clientlib - to etc/designs - and then do a tree activation, the next time we request a webpage that includes those font files, then the font files are created in the dispatcher with file size 0. The resulting impact is that when requesting a web page in the browser, font files are not properly downloaded (browser reports "Failed to decode downloaded font:")
We can work around this issue by connecting to the dispatcher and manually removing the font files before re-requesting them (when they are subsequently cached and served correctly). In front of our Apache dispatchers we use Cloudflare as a CDN.
Is this a known problem with the dispatcher or likely to be a combination of the above (we also have CORS configurations in place to specifically allow cross origin use of the font files)?