The Chromium developers are still working on a fix for large image decoding causing memory use of more than 1 GB of RAM, so we are looking into adding a hack to get around the problem.
For any images over a certain file size, we want to open the image and check the resolution. If it is too large to decode safely in chromium then we want to swap it for a stock image that says the image needs to be resized.
Do we need to create our own CefResourceHandler for all http: and https: traffic, override events in the stock one, or do something else? Any suggestions and tips would be very helpful.