I think you are misunderstood. The cache subsystem memory bounding only
accounts for the objects stored in the cache itself (i.e. glyph outlines,
bitmaps, charmaps), but not the FT_Face and FT_Size objects themselves.
Iirc, you can purge the latter if you want without purging the cache objects
Hi Werner
Thanks alot for the reply. I have looked at your suggestion and tried to
understand how it works.
I have one question regarding this. I understand that after we set env
variable FT2_ALLOC_COUNT_MAX and FT2_DEBUG_MEMORY on runtime, the value for
FT2_ALLOC_COUNT_MAX will be assigned to
Does the above check aim to bound memory allocation to up to
table-alloc_total_max? If that is the case, should the check be the
following instead:
if ( table-bound_total
table-alloc_total_max - table-alloc_current (FT_ULong)size )
(1) static array: currently we know that all memory consumption by
freetype is done through malloc calls and its variants. However, is
there any other memory used in freetype, such as global arrays,
which are used for memory allocation? If so, do they need any kind
of configuration?
Yes,
Dear FreeType Developers,
I have a few questions regarding freetype memory consumption upper bound; I
am using Freetyper version 2.3.7
(1) static array: currently we know that all memory consumption by freetype
is done through malloc calls and its variants. However, is there any other
memory
