On Fri, Jun 15, 2001, Bill Nalen/Towers Perrin wrote:
> Does this mean that any failure in the uncompress (like I messed up writing
> the record) would cause this message?
Yes, actually anything resulting in a failure to display a document
will give you this alert. I like to keep things as simple as possible
and to give unique error messages for every possible error would be
more or less impossible.
> So it's not really about memory,
Most of the time the reason is really about memory.
> just that there was an uncompress error which needs to be figured out on
> its own? This is what I'm assuming.
There are not that many things that can go wrong in the uncompress
function (it's a short and simple function), so it shouldn't be that
difficult to find the problem.
Reasons for failure:
1. the size of the compressed data is *larger* than the size of
the uncompressed data
2. not possible to allocate the record used for storing the
uncompressed data
3. not possible to initializes the internal stream state for
decompression (i.e. inflateInit() fails)
4. not possible to allocate memory (1K) for uncompress buffer
That's it.
/Mike
