It is possible that the release method in BridgeFacesContext is no longer necessary:

if (null != responseWriter && compressDOM)

However, without it, it is likely that the DOM will persist in memory until the next request, thereby increasing the working memory required by the application. The fix for this is likely to uncompress the DOM just prior to applyBrowserDOMChanges()

Enable compressDOM in the auctionMonitor web.xml to reproduce:

<context-param>
<param-name>com.icesoft.faces.compressDOM</param-name>
<param-value>true</param-value>
</context-param>

Verified that this is not fixed. DocumentStore.load() is being called multiple times, thereby over-writing applyBrowserDOMChanges().

— src/com/icesoft/faces/context/BridgeFacesContext.java (revision 18074)
+++ src/com/icesoft/faces/context/BridgeFacesContext.java (working copy)
@@ -437,6 +437,7 @@
}
}
}
+ documentStore.save(document);
}

This fixes the functional aspect of the bug, however there is a redundant call to documentStore.save during user input (first in applyBrowserDOMChanges and again at the end of the cycle). This should be optimized.

ested successfully on ICEFaces 1.8.1 build 1 + Glassfish v2.1 using component-showcase facelets-enh

Browsers tested: Opera9.64, IE8, FF3