Working with sIEve I created a tiny GWT application to replicate an apparent IE pseudo-leak in my larger application. In my GWT test application I was able to clearly reproduce a pseudo-leak. I diagnosed this because sIEve showed consistent linear growth in size and in-use count of orphaned of DIV and FORM nodes. I posted the entire Eclipse GWT project to GWT issue 2023: http://code.google.com/p/google-web-toolkit/issues/detail?id=2023
However, in further testing I allowed the "leaking" code to run in IE (outside of sIEve) for several hours. Strangelt *no* actual leaking occurred, the memory in use actually shrank slightly. Is there a known issue with sIEve reporting orphaned nodes as in use for perpetuity when IE is actually correctly and successfully collecting them?
I am running IE 6.0.2900.2180.xpsp_sp2_gdr.070227-2254 and sIEve-0.0.8
Log in to post a comment.