[Tremor] running memory size is not predictable?

[Park Jin Soo]

Is it possible to predict the maximum size of running memory in tremor?

For example, in vorbis_staticbook_unpack(),
s->lengthlist is allocated as bellow,

  s->entries=oggpack_read(opb,24);
...
    s->lengthlist=(long *)_ogg_malloc(sizeof(*s->lengthlist)*s->entries);

This seems to mean that the size can be 16777215 * sizeof(long) bytes!!!???
In this way, the predicted value for running memory is too large.
Are there any other restrictions to memory size in spec. or encoder?
How can I predict the exact and proper limit of running memory?

Thanks in advance and best regards,
Jin Soo




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/tremor/attachments/20051014/7fdcfc38/attachment.htm