When a web page is running at the maximum STB’s memory and/or processing capacity, developers might find that Liberate’s TV Navigator browser does not behave consistently and the application (in Emmy or on the STB) may freeze.

Below is a list of indicators that a site, selection of pages or single page may be causing memory problems:

• Emmy/STB crashing whilst navigating site. This is not necessarily associated with a particular action/object and there may be no error messages displayed in the debug window (or logged in the emmy.log file, found in the emmy install folder). This may occur immediately after the page loads or while navigating site for a length of time.
• Messages such as below may be displayed in the Emmy debug window; if the text of the error message contains the word "memory", then developers can assume a memory error. e.g.

INVOKING ERROR HANDLER: -------------------------------
Error Type: (memory)
Error Code: (text/html)
Victim is a DocWidget, type is (area)
Victim Type: (window)
Bad URL (http://www.any-domain.com/index.html)
------------------------------------------------------------------------------

• Images randomly/intermittently failing to display when Emmy debug info confirms the image has been requested and received.
• Images being partially rendered or not displaying correctly
• The Emmy debug window shows an "Error 2" or "NO_ROOM" this means that the DTV Client has run out of memory or failed to allocate memory correctly.

Hints & Tips

• Remove objects/code piece by piece from a specific web page and check each time that the error still occurs. Do this until you can identify which specific function/item is causing the error.
• See the “How To” pages covering reduction of code and image memory usage.