Re: Compression memory

[Bill Nalen/Towers Perrin]

Does this mean that any failure in the uncompress (like I messed up writing
the record) would cause this message?  So it's not 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.

Thanks




                                                                                       
                     
                                                                                       
                     
                                         To:     Plucker Development List 
<[EMAIL PROTECTED]>   
                    Michael              cc:     (bcc: Bill Nalen/Towers Perrin)       
                     
                    Nordstr�m            Subject:     Re: Compression memory           
                     
                    <micke@sslug.                                                      
                     
                    dk>                                                                
                     
                                                                                       
                     
                    06/15/2001                                                         
                     
                    12:21 PM                                                           
                     
                    Please                                                             
                     
                    respond to                                                         
                     
                    Plucker                                                            
                     
                    Development                                                        
                     
                    List                                                               
                     
                                                                                       
                     
                                                                                       
                     



On Thu, Jun 14, 2001, Bill Nalen/Towers Perrin wrote:
> I'm curious though since it only happens on one page of many and it's not

> the largest page by any means.

If this happens when you open a new document then it is because the
viewer failed to uncompress the page.

In ViewHtmlDocument (document.c) there is a call to the uncompress
function (for ZLib compressed documents it will use the UnZip function
in uncompress.c) and if it for some reason fails to uncompress the
document it will return false to ViewDocument that will return this
status code to the event handler for the main form and the alert will
be displayed. Search for 'warnInsufficientMemory' in the source code
and you will find all places where this alert could appear.

/Mike