Memory Requirements and Considerations







Memory requirements for rendered web pages directly relate to the minimum physical size in pixels required to render the entire page. Page rendering is a dynamic process, and browsers calculate the minimal page size by performing multiple measuring and reformatting passes (reflowing), measuring font and image sizes as they go, and adjusting positions of page content during each pass until no further reflowing is necessary.

Please note: When using saveToBufferedImage the memory requirements of Java for buffered images can be large. If you receive an outOfMemoryException you need to increase your JVM heap size (-Xmx64M), or alternatively use the IBrowserCanvas savePageImageToDisk method.


WebRenderer Server Edition renders web pages, in their entirety, to bitmapped images. This is quite unlike interactive browsers that are able to render only the visible subset (or thereabouts) of a page, as required. WebRenderer Server Edition is designed to render and return the entire page as single image, but does also provide for rendering a subset of a page to a target bitmap size (see Set Size).

Extremely large web pages may be impossible to render due to the memory requirements of a single large image. For example, we could not reasonably expect to render an entire page requring 100GB of memory for a bitmap large enough to contain it. The world's longest web page claims to be 1010km long; a bitmap of this size would be prohibitive, and consequently WebRenderer should place restrictions on the size of the rendered image for this site. In cases where there is not enough memory to create a bitmap large enough,
WebRenderer Server Edition will return a null.










 Copyright � JadeLiquid Software - www.jadeliquid.com