Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Processing images can take considerable amounts memory, and running out of memory can impact the entire application. It would be great to have a mechanism to make sure image processing remains within 'reasonable' bounds, and fail gracefully when it exceeds them. Of course what is 'reasonable' is application-dependent.
This issue exists to track the ideas and experiments around implementing such a mechanism, which will likely have impact on various APIs. The 'Allocator' API on the master branch is the current work towards this goal.
Potentially interesting testcases for this infrastructure include:
Attachments
Issue Links
- relates to
-
IMAGING-365 Extend oss-fuzz to cover Imaging class
- Open